Jump to content
  • Advertisement

Archived

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

penetrator

.NET trouble with Visual Basic

This topic is 5970 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I have a project which build and run correctly on my pc. However, when i run the .exe on another pc, i get ''set registry key HKLM\Software\Microsoft\.NETFramework\InstallRoot to point to the .NET Framework install location'' Is there a way to disable this Framework or a workaround to this error ? Thanks
www.web-discovery.net

Share this post


Link to post
Share on other sites
Advertisement
You can''t do that.

VB.NET compiles programs that run on the .NET framework. VB.NET is incompatible with VB6.

If the .NET framework is not installed, the program won''t run. Simple as that.

Rewrite in VB6 or Install .NET framework, those are your options.

Share this post


Link to post
Share on other sites
Wait a second here.

If I write a program in .NET just as I would in VB6 and try to distribute the Release executable (if such a profile concept still exists in .NET) to a few friends or whomever, then it won''t run unless they have the .NET framework installed? Is there something I''m missing? That sounds like shit, but not unlike Microsoft.

Share this post


Link to post
Share on other sites
It''s not shit. You still need the VB6 runtime to run VB6 programs, even in release mode. The VB6 runtime is just a bit smaller than the .NET one.

VB.NET is a .NET language. So is C#. So is managed C++. That means to run programs written any of these languages you need the .NET runtime. (The exception in unmanaged C++. C++ is the only ".NET" language which can run in native mode and doesn''t require the runtime to run)

It''s only a 20MB or so download, and it''ll be included in the next Windows XP service pack anyway, so it''s really not that big a deal.

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
Simple solution then: don''t use VB.NET. It''s not like Microsoft tried to hide the fact that you also need the .NET runtime to use .NET languages. Heck, that''s why it''s called the .NET "runtime".

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

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!