Building w/ Visual Studio 2010

[thelists]

I've downloaded the 1.0.8.2 source and am trying to compile it under VS2010. Has anyone done this successfully yet? To be honest, most of my development is on on the Linux side, using eclipse, so I may be doing something incorrectly.

I open the winvnc project in VS2010, set it to debug or release and have it build. Many of the components compile successfully, but a few fail, such as "logmessages":

Code: Select all

1>  Touching ".\..\..\Release\logmessages.unsuccessfulbuild".
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5): warning MSB8012: TargetPath(C:\Users\xx\Documents\Visual Studio 2010\Projects\UltraVNCtest2\winvnc\logger\.\..\..\Release\logmessages.dll) does not match the Linker's OutputFile property value (C:\Users\xx\Documents\Visual Studio 2010\Projects\UltraVNCtest2\winvnc\logger\messages.mc). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(991,5): warning MSB8012: TargetExt(.dll) does not match the Linker's OutputFile property value (.mc). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(992,5): warning MSB8012: TargetName(logmessages) does not match the Linker's OutputFile property value (messages). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
1>LINK : fatal error LNK1181: cannot open input file 'messages.res'

Also, ipp_zlib failed to convert, with VS2010 complaining that ipp_zlib.vcproj was unable to be found.

Any quick suggestions? Did I miss something in other forum posts?

[thelists]

Also, just tried with SVN code. Complains about 'Flasher.cpp' being not found and fails for vncviewer. Haven't tried yet for winvnc SVN.

[Rudi De Vos]

remove it from the project
This file isn't used

[teacherwilli]

Hey,

I even have a problem with building a winvnc release with vs 2008 or 2010:
I got no error after building, but if I start the winvnc.exe an error occures with the message: "Diese Anwendung konnte nicht gestartet werden, weil die Anwendungskonfiguration nicht korrekt ist."
("EXe couldn´t be started because the configuration of the application isn´t correct.")
I even installed the microsoft vs redistributable package.

[Rudi De Vos]

Remove the manifest file from the resources or make sure the embedded manifest is the same as the processor..

In VS2010 we don't need the manifest file, all can be set via VS

[teacherwilli]

Thank you!
Is there a projectfile (winvnc.sln ?), a file that contains all settings, for VS 2010 available?