[Winmerge-svn] SF.net SVN: winmerge: [4117] trunk/Docs/Developers

[<ki...@us...>]

Revision: 4117
          http://svn.sourceforge.net/winmerge/?rev=4117&view=rev
Author:   kimmov
Date:     2007-02-19 14:32:17 -0800 (Mon, 19 Feb 2007)

Log Message:
-----------
Add short instructions for Visual Studio 2005

Modified Paths:
--------------
    trunk/Docs/Developers/Changes.txt
    trunk/Docs/Developers/readme-developers.html

Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt	2007-02-19 21:41:00 UTC (rev 4116)
+++ trunk/Docs/Developers/Changes.txt	2007-02-19 22:32:17 UTC (rev 4117)
@@ -1,6 +1,8 @@
 2007-02-19 Kimmo
  Bugs 1663767-1663770, 1663776, 1663778: typo/grammar fixes.
   Developers: readme-developers.html
+ Add short instructions for Visual Studio 2005
+  Developers: readme-developers.html
 
 2007-02-12 Tim
  PATCH: [ 1658347 ] Add note about PSDK paths and VC into dev-readme

Modified: trunk/Docs/Developers/readme-developers.html
===================================================================
--- trunk/Docs/Developers/readme-developers.html	2007-02-19 21:41:00 UTC (rev 4116)
+++ trunk/Docs/Developers/readme-developers.html	2007-02-19 22:32:17 UTC (rev 4117)
@@ -191,7 +191,19 @@
   <li>Plugin dlls : Unicode Release MinDependency</li>
 </ul>
 
+<h4>Visual Studio 2005</h4>
+<p>When VC6 project file (.dsp) is converted to Visual Studio 2005 project, it does not
+compile correctly as is. The problem is Visual Studio 2005 automatically generates and
+embeds manifest file for the executable. And as WinMerge resource file includes manifest
+file there are conflicts.</p>
 
+<p>The easiest way to fix the compile is to disable VS2005 from creating and embedding
+the manifest file. From project properties:
+<ul>
+  <li>disable Linker / Manifest File / Generate Manifest (set to "No")</li>
+  <li>disable Manifest Tool / Input and Output/ Embed Manifest (set to "No")
+</ul></p>
+
 <h3><a name="Code_changes">Code changes</a></h3>
 
 <p>Please follow these guidelines when submitting changes to WinMerge sources


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.