Is there a simple way....

Hot Topic

msvcr80.dll Problem
Wrapping Unmanaged Library - Options.
c1083 fatal error cannot find include file
VS2005 porting issue
c1083 fatal error cannot find include file
Can C++ develop web-based applications?
command line build up-to-date when it shouldn't be
calling managed code from unmanaed
Multithreading
Convert wchart_t to TChar

Visual C++

Pause in action with MSVC++.NET
Problem with .NET runtime
Web Browser
Smartbridge Alerts
Active X
How to Stop Windows from updating mouse position automatically
msvcr80.dll Problem
Missing WM_CLOSE Message
Problem with templates
Array of pointers to Chars

Is there a simple way....

Is there a simple way to target native Win32 when compiling C++ code in VS2005 Beta 2

Basically the situation is that I have my own C++ code, which uses functions from the Irrlicht graphics library and the RakNet networking library. Irrlicht uses a DLL and a static lib, RakNet just a static lib, all of which were provided with the downloads: I haven't recompiled anything. There is absolutely no code in there that SHOULD require the .NET Framework, but no matter what options I choose in the project properties, when I come to deploy my application, if the .NET Framework is not already installed, it asks for it. My app is very simple, less than 1MB in size, so I'd really like to be able to avoid my users having to download an extra 30MB for the Framework before they can run it.

Would compiling using VS2003 make a difference I'd prefer not to have to switch back to the older environment, but if I have to, I will. I was trying to compile using the VC++ Toolkit but I got lost in command-line switches :(

Answer this question

Is there a simple way....

  • Mohankrish

  • nandinho

    Actually,
    There are two options in the VS 2005 menu.  One is to include CLR support (/CLR) and the other is to require the .NET Runtime Libraries.  Make sure both of these are turned off and you will be good to go.

  • Gary Harrison

    Yeah, I do. But, no matter whether I use the /CLR switch or not, my resulting EXE file still requires .NET 2.0 Sad

    I thought I had it fixed there, when I rebuilt using the /CLR switch and #pragma unmanaged, my deployment project told me it wasn't dependent on .NET - but the installer still asked me to install it (I'm using VMWare to give myself a basic platform on which to test).

    So, any more suggestions

  • Abadisoft

    What are you using to generate the setup file You should ensure that none of your files are being compiled with the /clr switch. Indeed, even though you set that correctly in your project properties, individual files can override switches. An easy way to verify this would be to look at your buildlog file and verify that the string '/clr' never appears.

  • JaysonGo

    Something strange I've just come across. It only appears to be the setup file that requires .NET 2.0 - I've just done another rebuild of my deployment - launching the setup.exe pops up the window asking me to install .NET Framework 2.0 Beta, as it always has in the past. HOWEVER, launching the .MSI file directly didn't require me to install .NET, and the application seems to run correctly.

    Why would this be the case

  • osydney

    Ok - where should I be looking for this other option I can't seem to find it Tongue Tied
  • Is there a simple way....
Answer this question