Native win32 apps still require .NET runtime?

  • Thread starter Thread starter Dave
  • Start date Start date
Maybe your old manifest isn't compatible with VC2005 or something.

If all else fails, I would use VC2005 AppWizard to generate a new project
and then add all your source files. Maybe your project wasn't converted
properly.
Click to expand...

Actually this is a new test app, generated under VS2005. My skilled
team of designers and programmers went away for 12 days and came back
with:

#include "stdafx.h"
#include <stdio.h>

int _tmain(int argc, _TCHAR* argv[])
{
printf("Hello World\n");
return 0;
}

Someone accused them of plagiarism, but I'm not buying it.

Seriously, you don't even need the stdio.h or printf. A completely
stock untouched, empty Win32 console app will fail to run on our test
machine.
 
Dave said:
Maybe your old manifest isn't compatible with VC2005 or something.

If all else fails, I would use VC2005 AppWizard to generate a new project
and then add all your source files. Maybe your project wasn't converted
properly.
Click to expand...

Actually this is a new test app, generated under VS2005. My skilled
team of designers and programmers went away for 12 days and came back
with:

#include "stdafx.h"
#include <stdio.h>

int _tmain(int argc, _TCHAR* argv[])
{
printf("Hello World\n");
return 0;
}

Someone accused them of plagiarism, but I'm not buying it.

Seriously, you don't even need the stdio.h or printf. A completely
stock untouched, empty Win32 console app will fail to run on our test
machine.
Click to expand...

I just ran across http://blog.kalmbachnet.de/?postid=54 which says, "If you
build your app with VC2005 and you accidently have disabled the embedding of
the manifest file (or deleted the separate appname.exe.manifest file), you
will get an error on XP and later!"

-- David
http://www.dcsoft.com
 
The recommendation in this article only applied to Beta 2 release and
applocal deployment. Please see VC docs on MSDN on how to deploy VC++
applications. Here are examples on how to deploy apps,
http://msdn2.microsoft.com/en-us/library/ms235285.aspx and overall section
describing supported policies for redistribution of VC++ libraries,
http://msdn2.microsoft.com/en-us/library/ms235316.aspx.

Nikola

--
Nikola Dudar
Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Suggestions? Bugs? Talk directly to dev teams using
http://lab.msdn.microsoft.com/productfeedback/
My Blog - http://blogs.msdn.com/nikolad/
 
Deploying VC++ DLLs into System32 is wrong way to redistribute VC++
libraries. Please review Deployment section of VC++ docs,
http://msdn2.microsoft.com/en-us/library/ms235316.aspx where you may find
examples on how to deploy apps,
http://msdn2.microsoft.com/en-us/library/ms235285.aspx

Nikola VC++


--
Nikola Dudar
Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Suggestions? Bugs? Talk directly to dev teams using
http://lab.msdn.microsoft.com/productfeedback/
My Blog - http://blogs.msdn.com/nikolad/
 
I just ran across http://blog.kalmbachnet.de/?postid=54 which says, "If
you build your app with VC2005 and you accidently have disabled the
embedding of the manifest file (or deleted the separate
appname.exe.manifest file), you will get an error on XP and later!"
Click to expand...
Correct. Same is stated in the VC docs,
http://msdn2.microsoft.com/en-us/library/ms235316.aspx

In order for you application to run on a computer that does not have VS
installed, same as in VC6, VC7.x, in VS2005 you need to redistribute VC++
runtime libraries. The supported ways are documented in Deployment section
of VC docs,
http://msdn2.microsoft.com/en-us/library/zebw5zk9.aspx

Nikola

--
Nikola Dudar
Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Suggestions? Bugs? Talk directly to dev teams using
http://lab.msdn.microsoft.com/productfeedback/
My Blog - http://blogs.msdn.com/nikolad/


David Ching said:
Dave said:
Maybe your old manifest isn't compatible with VC2005 or something.

If all else fails, I would use VC2005 AppWizard to generate a new project
and then add all your source files. Maybe your project wasn't converted
properly.
Click to expand...

Actually this is a new test app, generated under VS2005. My skilled
team of designers and programmers went away for 12 days and came back
with:

#include "stdafx.h"
#include <stdio.h>

int _tmain(int argc, _TCHAR* argv[])
{
printf("Hello World\n");
return 0;
}

Someone accused them of plagiarism, but I'm not buying it.

Seriously, you don't even need the stdio.h or printf. A completely
stock untouched, empty Win32 console app will fail to run on our test
machine.
Click to expand...

I just ran across http://blog.kalmbachnet.de/?postid=54 which says, "If
you build your app with VC2005 and you accidently have disabled the
embedding of the manifest file (or deleted the separate
appname.exe.manifest file), you will get an error on XP and later!"

-- David
http://www.dcsoft.com
Click to expand...
 
Back
Top