Package that includes only what is needed

[timothy]

Using a tutorial in .NET I figured out how to package up a project for redeployment at a real high level. The package I created will require MDAC and .NET Framework be downloaded from MS before install. Isn't this kind of overkill? All I need is a few ODBC drivers and the namespace dll’s used in the application.

Can someone give me a clue as far as what to do to include the necessary namespaces and drivers with the package?

Any help is appreciated.

Thanks

 

[chiph]

All .NET apps require the framework on the target machine. If you're 100% sure your target machines will already have it installed (perhaps they already have Office 2003 on them), then you can remove it from your install package.

Otherwise, they'll either need to get it via another MS package (ie. Office), Windows Update, MSDN download, or via your .msi file.

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first

 

[timmoser]

Thanks, so they will have to download the framework and MDAC to I guess. There is no way to just pull what the app needs? We have a simple little app that would fit on a floppy disk! Seems like a waste to burn or download the entire MDAC and framework.

Thanks for your help.

 

[chiph]

That's what people have been complaining about ever since the framework came out.

"What do you mean I have to ship a 20mb runtime!!??!!"

I heard the same thing back in the Win95 days when you had to ship the DCOM95 redistributable with your app. The more things change, the more they stay the same!

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first