Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What tools are available to determine which .NET assemblies have changed since the last build?

With a seriously big .NET site/solution (100's of assemblies), are there any tools available to recognise which assemblies have changed since the last build (using something more intelligent than file dates that will always change).

I need to change our deployment process to a) increment the version of changed assemblies and b) generate a delta release to include these modified assemblies.

My current approach for our ASP.NET web site and Biztalk servers is to re-deploy the full solution after a build - this can take up to 3 hours (most of the time is spent undeploying and redeploying the BizTalk applications).

Microsoft recommend that we version our assemblies and only deploy those assemblies that have changed to reduce our deployment window. I would like to automate this as much as possible.

We are currently using MSBuild, TFS and good "old fashioned" people to manage our build process.

like image 362
Jon Simpson Avatar asked Dec 03 '08 15:12

Jon Simpson


People also ask

How do I know if .NET is updated?

The installed security updates and hotfixes for each version of the . NET Framework installed on a computer are listed in the Windows registry. You can use the Registry Editor (regedit.exe) program to view this information.

Which is used to determine the Application dependencies in assemblies?

The assembly manifest describes the version dependencies you specify for any dependent assemblies. For more information about versioning, see Assembly versioning. The deployment unit: When an application starts, only the assemblies that the application initially calls must be present.


1 Answers

Have a look at NDepend. I believe you can use it to generate reporots of just that sort of thing and use these as inputs to your deployment process

like image 61
Rad Avatar answered Nov 15 '22 00:11

Rad