two PowerPack questions

[C]

PowerPack seems necessary for CommonDialogs, PrintForm, etc.

Can I copy a file or two along with *.exe to circumvent packaging the
program? In the good old days, we used to copy VBRUN300.DLL with the
*.exe, and that was all that was needed. Is there something similar
now, may be with three or four files instead of just one?

Why is most of the VB.net supporting code already there in Windows XP,
Vista, etc. but not the code for PowerPack?

Thanks.

 

[J.B. Moreno]

PowerPack seems necessary for CommonDialogs, PrintForm, etc.

Can I copy a file or two along with *.exe to circumvent packaging the
program? In the good old days, we used to copy VBRUN300.DLL with the
*.exe, and that was all that was needed. Is there something similar
now, may be with three or four files instead of just one?

I'd suggest just going with the flow and creating a setup project.
They aren't that hard to do and they will include the files you need
and put them in the right places.

Why is most of the VB.net supporting code already there in Windows XP,
Vista, etc. but not the code for PowerPack?

No idea, IMO they should have folded it into the main framework a long
time ago.

 

[C]

I'd suggest just going with the flow and creating a setup project.
They aren't that hard to do and they will include the files you need
and put them in the right places.  

I of course know of this option, but I would also like to know what it
does - which files it copies, and preferably also why it needs those
files. Are there just a few files or are there dozens, if I have used
say, only PrintForm?

Thanks.

 

[J.B. Moreno]

-snip use setup project-

I of course know of this option, but I would also like to know what it
does - which files it copies, and preferably also why it needs those
files. Are there just a few files or are there dozens, if I have used
say, only PrintForm?

I'd guess only one or two, I don't know for sure. If you create a
setup project, it will let you know what files are going to be part of
it.