By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,837 Members | 1,648 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,837 IT Pros & Developers. It's quick & easy.

What happened to the Setup and Deployment Wizard?

P: n/a
dp
I just started using VB.NET and am trying to go through a complete
test project. I did some db stuff, added a crystal reports form for
output and the program runs as it should. Now how do I create a setup
package to run on other computers?

Does .NET use only the Windows Installer process? VB6 had a Setup and
Deployment Wizard that collected all dependants and you could add
extra things like readme files and the like. Then it packaged the
whole thing into cab files and a setup.exe file. Is there such a thing
for .NET?

If I need to use the WI process, how does that work on older systems?

Thanks,
Dan P.
Jul 17 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Almost everybody here is using VB6 or lower. While you may get a stray
answer to VB.NET questions here, you should ask them in newsgroups devoted
exclusively to .NET programming. Look for newsgroups with the word "dotnet"
in their name.

For the news.devx.com news server, try these

vb.dotnet.discussion
vb.dotnet.technical

For the microsoft news server, try these newsgroups...

microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb

There are some others, but these should get you started.

Rick - MVP


"dp" <da**@solidservices.net> wrote in message
news:d1**************************@posting.google.c om...
I just started using VB.NET and am trying to go through a complete
test project. I did some db stuff, added a crystal reports form for
output and the program runs as it should. Now how do I create a setup
package to run on other computers?

Does .NET use only the Windows Installer process? VB6 had a Setup and
Deployment Wizard that collected all dependants and you could add
extra things like readme files and the like. Then it packaged the
whole thing into cab files and a setup.exe file. Is there such a thing
for .NET?

If I need to use the WI process, how does that work on older systems?

Thanks,
Dan P.

Jul 17 '05 #2

P: n/a
I don't know how .Net does it. You'll need to ask in
a .Net newsgroup.

WI works on older systems but requires the WI runtime
(about 1.5 MB I think). Unfortunately, it's also designed
not to work unless the equivalent runtime is installed. Many
older systems have some version of WI but far fewer will have
the latest version.
You might want to use an older version of WI if you want to
avoid forcing most of your users to download the WI runtime.
On the other hand, if you're using .Net then I guess you're
going to be sending the .Net runtime to most machines, anyway.
In that context the WI runtime would be a drop in the bucket.

Microsoft seems to be switching over to WI and some
of the third-party installer programs now are actually WI editors.
I would guess that the fabled Longhorn will require WI installs
because it allows for a standardized system to control DLL
versioning, Registry installation records, etc. It also gives MS
a way to exert control over everything installed on a system.

WI uses a database file (.MSI) to package your program along
with all of the necessary details. The database setup is so complex
that most people use a third-party program to deal with it, although
you can do it yourself. There's an automation interface for it and
there's a free, script-based MSI editor around called "iszfree".
MS also has a WI SDK.

Personally, I would look for a way to avoid the whole WI mess.
In my opinion, WI is so overproduced that it goes beyond silly to the
point of irritating....but it IS the new standard.
--
--
dp <da**@solidservices.net> wrote in message
news:d1**************************@posting.google.c om...
I just started using VB.NET and am trying to go through a complete
test project. I did some db stuff, added a crystal reports form for
output and the program runs as it should. Now how do I create a setup
package to run on other computers?

Does .NET use only the Windows Installer process? VB6 had a Setup and
Deployment Wizard that collected all dependants and you could add
extra things like readme files and the like. Then it packaged the
whole thing into cab files and a setup.exe file. Is there such a thing
for .NET?

If I need to use the WI process, how does that work on older systems?

Thanks,
Dan P.

Jul 17 '05 #3

P: n/a
Once you are finished, go to the File menu and add a new project. The
Dialog box will come up, and from there, pick Setup Wizard project.
Follow the prompts. The new setup package is one of the only things I
like about .net.

"dp" <da**@solidservices.net> wrote in message
news:d1**************************@posting.google.c om...
I just started using VB.NET and am trying to go through a complete
test project. I did some db stuff, added a crystal reports form for
output and the program runs as it should. Now how do I create a setup
package to run on other computers?

Does .NET use only the Windows Installer process? VB6 had a Setup and
Deployment Wizard that collected all dependants and you could add
extra things like readme files and the like. Then it packaged the
whole thing into cab files and a setup.exe file. Is there such a thing
for .NET?

If I need to use the WI process, how does that work on older systems?

Thanks,
Dan P.

Jul 17 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.