• 0

Redist'ing VB.NET Stuff


Question

I'm writing a basic program with VB.NET 2003 that will be distributed for CD use only. Do the people who stick this program inside their CD Drive have to have the .NET Framework installed, or can I somehow tell my program to look for a few runtime files that I can include on the CD?

Any sites that explain this as well?

Thanks! :D

Link to comment
Share on other sites

18 answers to this question

Recommended Posts

  • 0

You mean the CD will contain the actual program and not an installer? Then yes, the framework must be installed before they can use it :yes: Otherwise, you can include the framework with your install (Y)

Link to comment
Share on other sites

  • 0
You mean the CD will contain the actual program and not an installer? Then yes, the framework must be installed before they can use it :yes: Otherwise, you can include the framework with your install (Y)

So I can't just include that runtime file like with VB6?

Link to comment
Share on other sites

  • 0
You can put it on the CD, but they'll have to install it before they can use your program.

Well thats kinda stupid... :huh:

All the computers here have the .NET Framework 1.0.3705 installed on them. My company is really anal about installed non-approved software on their machines. Will stuff that I build with VB.NET 2003 work with that version of the frame work on it?

Thanks!

Link to comment
Share on other sites

  • 0

yes and no. if you use features from the .net 1.1 release then no the app is most likely not to work on a system w/ .net 1.0. however if you only use 1.0 classes etc then your app may run just fine.

Link to comment
Share on other sites

  • 0

anything done using 2.0 beta will not work w/ either 1.0 or 1.1. I have recently found this out the hard way when my beta tester couldn't run my app after switching to C# Express

Link to comment
Share on other sites

  • 0
anything done using 2.0 beta will not work w/ either 1.0 or 1.1. I have recently found this out the hard way when my beta tester couldn't run my app after switching to C# Express

None of the really simple apps work with the version of the framework that my company has installed...

Looks like it's back to VB6 :unsure:

Link to comment
Share on other sites

  • 0
None of the really simple apps work with the version of the framework that my company has installed...

Looks like it's back to VB6 :unsure:

If you're writing software with VS .NET 2003 and you are going to distribute it via CD then all you need to do is learn how to use MSI.

Inside of Visual Studio .NET Create a Deployment project.

Add yoru project to it and tell the installer to check for .NET Framework version and install if necessary.

If everything is done properly in code then the Installer will Install the Newer Framework first and then Install your software afterwards.

You can also use a program like InstallShield Developer or Express which are IDE completely made for MSI (Windows Installer) which make this easier.

Link to comment
Share on other sites

  • 0
If you're writing software with VS .NET 2003 and you are going to distribute it via CD then all you need to do is learn how to use MSI.

Inside of Visual Studio .NET Create a Deployment project.

Add yoru project to it and tell the installer to check for .NET Framework version and install if necessary.

If everything is done properly in code then the Installer will Install the Newer Framework first and then Install your software afterwards.

You can also use a program like InstallShield Developer or Express which are IDE completely made for MSI (Windows Installer) which make this easier.

Like I said...

I CAN'T Install ANY updated software. I have to work with what's there

Link to comment
Share on other sites

  • 0

why bother switching to vb6 when you can write all the vb.net code you want in vs2003 so long as you stay to the 1.0 framework and use the 1.0 vb.net cmd line compiler. sure its a little extra work, but in the long run worth it.

Link to comment
Share on other sites

  • 0
why bother switching to vb6 when you can write all the vb.net code you want in vs2003 so long as you stay to the 1.0 framework and use the 1.0 vb.net cmd line compiler. sure its a little extra work, but in the long run worth it.

OMG...

How can you use the 1.0 command line thingy????

Link to comment
Share on other sites

  • 0
There should be an option in the project properties as to which version of the framework that assembly requires (Y)

Tried that as well...

Still doesn't seem to build and work. :no:

Link to comment
Share on other sites

  • 0

Then you can use the compiler from the 1.0 SDK like quadsoft was saying, but that's not exactly as fun as using VS :(

Link to comment
Share on other sites

  • 0
Then you can use the compiler from the 1.0 SDK like quadsoft was saying, but that's not exactly as fun as using VS :(

... and is there a site that will show how???

Link to comment
Share on other sites

  • 0

One thing you could do is create a stub in a language that creates native code (like C/C++) which runs your .NET application under its process space, and points the .NET application to the correct location to look for the files needed to run (kind of like a very simple loader). This seems possible, but I don't really know how to do it since I don't know what exactly the .NET framework requires (the CLR and the base class libraries, but what files exactly?) Just an idea. :unsure:

bwx

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.