• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 512
  • Last Modified:

How to deploy JUST changed precompiled binaries to live ??

Hi All,

I need a way to deploy just changed binaries in a precompiled setup ie my deployed files as "fixed named and single page assemblies". Visual studio typically wants to republish everything which I find troublesome since with a big application one might deploy an old version of a programme unrelated to the upgrade

I have Dev, Test and Live source copies on my local machines plus live build and I have a test and live remote server. For ease I copy up source onto test and I can then use a tool like "beyond compare" to identify all my changed files and only copy those up. This works extremely well. The problem is that this approach does not work with precompiled dlls as on my live server. If I have a small number of changed dlls I can remember them, but this is hardly a robust process.

I have a feeling that one can only publish everything in VS 2008 and not deltas. Alternatively are there tools that can tell the difference between 2 binaries ie which is different excluding the binary header as these always seem to be different when you recompile. File size and timestamps are unreliable.

Thoughts, ideas please.

Cheers,

Sam
0
SamJolly
Asked:
SamJolly
  • 4
  • 4
2 Solutions
 
Alfred A.Commented:
You can try using Scheduled Tasks function in your server to automate the copy of dlls only into your web site.  

http://support.microsoft.com/kb/814596

http://www.iopus.com/guides/winscheduler.htm
0
 
SamJollyAuthor Commented:
Thanks for the reply.

However my question is not about scheduling. It is about how to identify which asp.net dlls have changed using criteria other than timestamp and filesize. Apologises if I did not make myself clear.

Thanks,

Sam
0
 
Alfred A.Commented:
OK.  No worries.  I believe I misunderstood your question.  :-)

Anyway, have you tried using the Copy Web Site Tool?  It has a synchronization feature that might help you somehow achieve what you are trying to do.

Check the links below for details:

http://msdn.microsoft.com/en-us/library/1cc82atw.aspx

http://msdn.microsoft.com/en-us/library/c95809c0.aspx

http://msdn.microsoft.com/en-us/library/xay0wxbf.aspx

Regarding comparing two binaries, I use my own created tool to compare binaries but I haven't used it for deployment purposes.  I am providing links to some sites that deals with binary file comparison and where I got ideas in my own binary compare tool.

http://www.codeproject.com/KB/files/JTBinCompare.aspx

http://support.microsoft.com/kb/320346

I hope this helps.

0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
SamJollyAuthor Commented:
Thanks for the reply. I think the copy site tool just deals with source code so not appropriate since I am trying to compare 2 published folders for different binaries.

The file compare tool looks interesting, but I really need a folder compare utility for binaries rather than a file compare. Beyond Compare is excellent as far as it goes, but it does not deal with ASP.NET binaries.

Perhaps I may need to reapproach them with the problem.

Sam
0
 
Alfred A.Commented:
OK.  For folder or directory level compare, have you heard about Windiff.exe utility?

Check this out:

http://support.microsoft.com/kb/159214
0
 
SamJollyAuthor Commented:
this seems to compare the ascii file, not binary??

However having looked at this I found:

 DUMPBIN  /RAWDATA  MyApp.EXE > first.txt
 DUMPBIN  /RAWDATA  MyApp.EXE > second.txt

Which removes the date and timestamp so norm binary folder compare files can be used. Have not tried it yet. But it may be a way to go.

Thanks,

Sam
0
 
Alfred A.Commented:
Yes.  DumpBin would be one way.  In the link (Windiff one) I provided, there are suggestions in there to compare binary files and folders such as "comp" command.  I am listing an excerpt from the example in the link I provided:

comp C:\Winnt\System32\*.dll \\DifferentComputerName\C$\Winnt\System32\*.dll
0
 
SamJollyAuthor Commented:
Hi Alfred,

Sorry to be away. Been busy. I thought I would close this issue and award you the points.

However I may come back to this issue.

Thanks,

Sam
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now