Archived

This topic is now archived and is closed to further replies.

supagu

visual studio .net compile release

Recommended Posts

right, i have .net, when i goto compile it includes debug dll''s, so it only works on pc''s who have visual studio, when i build a release, it also includes these anoyying dll''s and so... only works on pc''s wh ohave dll''s, so how do i stop it including these dll''s so it can work on other peoples pc''s?

Share this post


Link to post
Share on other sites
from the microsoft website:

"Non-developers need to install the .NET Framework to run applications developed using the .NET Framework.

In most cases, the creator of an application will alert you if you need to install the .NET Framework Redistributable to run the application. However, with the number of .NET Framework-connected applications on the market growing rapidly, we encourage you to install the latest version of the .NET Framework Redistributable if you haven''t already."

guess i''m going back to vc6 then :''(

Share this post


Link to post
Share on other sites
Probably it isn''t the .NET dlls that is the problem, but the Microsoft C-runtime, and that one is a (or can be used as) dll on MSVC 6 too.

Either use the tools ''Dependency walker'' to see which dlls you need to redistribute, or change the settings of your project to use either ''Singlethreaded'' or ''Multithreaded'' (without the word dll) and also make sure you don''t link against mfc, atl or any other of those libs.

Share this post


Link to post
Share on other sites
Since VS.NET is a new version of the compiler, the runtime dlls are also newer. Users will need to have MSVCP70.DLL and MSVCRT70.DLL (possibly others as well, like the newer MFC DLL) to be able to run VS.NET applications. It was the same when VS 6 came out - none of the current operating systems include the required runtime DLLs by default (since they didn''t exist when the operating systems were released) so you need to either include them with your application, or get your users to download them separately.

If I had my way, I''d have all of you shot!


codeka.com - Just click it.

Share this post


Link to post
Share on other sites

Hi

I had the same problem. When creating a new project, you can choose between "managed" and "unmanaged" ones. Only the managed projects create EXEs, that require the NET-Framework to be installed.
Try using an unmanaged project.

Hope that helps

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
even on release mode, visual studio .net includes special debug dll''s included in the .net frame work i guess.

Share this post


Link to post
Share on other sites
If the issue concerns linking with the Microsoft Visual C Runtime (MSVCRT.DLL), then there are certain analogous functions that you can use to eliminate dependency on the MSVCRT library. I think.

Share this post


Link to post
Share on other sites
You can easily solve the problem by distributing the Microsoft .NET Framework redist along with your program. Whereas the .NET Framework SDK can only be installed on 2k, XP, .NET, etc. the redist can be installed on 95+ (iirc) and implements the end user functionality necessary for someone to run a .NET-based application.

-- Exitus Acta Probat --

Share this post


Link to post
Share on other sites
It has nothing to do with .NET. Zilch. Zero. Nadda. Nothing. *insert angry rant about Microsoft''s wanton use of the ".NET" label*

MSVCP70.DLL and MSVCRT70.DLL are all you need to distribute to get everything happy and working. (I do this myself)

I''m hip because I say "M$" instead of "MS".

Share this post


Link to post
Share on other sites