Basic Installer Requirements
-
I'd love to see an article that demonstrates the most basic necessary objects to place an ap into an installer. I'm referring to the most standard Windows Installer kinds of elements:
- Check to see if user has at least the .Net Framework and the version is compatible
- Prompt user for install location and create new folder if none exists
- Ask user if they want a shortcut icon on the desktop/quicklaunch
- Ask the user if they want to view the readme
- Include an uninstaller
Thanks Still coaxing software out of the can after all these years...
-
I'd love to see an article that demonstrates the most basic necessary objects to place an ap into an installer. I'm referring to the most standard Windows Installer kinds of elements:
- Check to see if user has at least the .Net Framework and the version is compatible
- Prompt user for install location and create new folder if none exists
- Ask user if they want a shortcut icon on the desktop/quicklaunch
- Ask the user if they want to view the readme
- Include an uninstaller
Thanks Still coaxing software out of the can after all these years...
Hmm............. Given your handle is 'tanstaafl', would you be willing to pay for such informaiton :-D What languge would you want to see examples in? Or are you looking for a document describing WHAT do do versus a concrete example of how to do it? Are you concerned about setup file size (file compression is required)? Do you know if you need Windows Logo compliance (must use MSI if yes)?
-
Hmm............. Given your handle is 'tanstaafl', would you be willing to pay for such informaiton :-D What languge would you want to see examples in? Or are you looking for a document describing WHAT do do versus a concrete example of how to do it? Are you concerned about setup file size (file compression is required)? Do you know if you need Windows Logo compliance (must use MSI if yes)?
I certainly would offer whatever time and skills I have to offer in exchange for the knowledge of how to create a installer that will work correctly with a PC that has just the .NET Framework. I wrote a program in Visual Basic .NET and had a difficult time getting it to work on two other computers, one had just the framework, and the other had a full version of Visual Studio.NET. I finally dumped every file and folder pertaining to the program onto the pc with just the framework and it worked. Still coaxing software out of the can after all these years...
-
I'd love to see an article that demonstrates the most basic necessary objects to place an ap into an installer. I'm referring to the most standard Windows Installer kinds of elements:
- Check to see if user has at least the .Net Framework and the version is compatible
- Prompt user for install location and create new folder if none exists
- Ask user if they want a shortcut icon on the desktop/quicklaunch
- Ask the user if they want to view the readme
- Include an uninstaller
Thanks Still coaxing software out of the can after all these years...
It's sooooo much easier if you download the Visual Studio .NET 2003 bootstrapper plugin. Now you need not write your Win32 bootstapper code to check for framework version, MDAC components, or any of your other concerns. Just install the plug-in, create a new setup(deployment) project in the IDE, and point and click your way to an elegant installer! Rock-on.