I found this in another thread:
"IMO, it's better to check for .NET 3.5 and if it is not available, open the
standard .NET 3.5 download page from your installer so users can download
and install it."
HOW would I do that?
Printable View
I found this in another thread:
"IMO, it's better to check for .NET 3.5 and if it is not available, open the
standard .NET 3.5 download page from your installer so users can download
and install it."
HOW would I do that?
Hello,
I have created and uploaded a simple demo project for you:
http://www.lindersoft.com/projects/net35web.zip
Please COMPILE and RUN the project.
Does this help?
Friedrich
Thanks.
Can I change the %NET35 variable to check for .net 4.5?
Yes, no problem.
Check for $NET_FRAMEWORK_45$ instead of $NET_FRAMEWORK_35$
Friedrich
Thanks. That's what I did:
Perfect!
Friedrich
Can I do something similar with SQL Server Express?
Our app checks for SQL the first time it is run and requires the installation of SQL if it is not found. Could I make SQL an optional installation? If they missed it during the initial install and got our error banger they could go back to the installation program and install SQL Express? I was going to include SQL Express on the installation medium - probably a jump drive.
On a side note, we would also need to run a script to install a SQL database after SQL server is installed. We are also doing that inside our app right now but it would probably be better handled as part of the setup.
Hello,
Absolutely no problem. But it depends on the SQL Server Express version. Would you like to check for 2012 or a previous version?
BTW, to run a script, just call the sqlcmd.exe tool from your install (e.g. from the "Run Command Line" or "Run Program" functions) and you are done.
http://technet.microsoft.com/en-us/l.../ms180944.aspx
Friedrich
We don't really care what version of SQL is installed. Can we check for any version? Or do we have to check for specific versions?
Is it possible to install .net from the installation media?
Hello,
It depends on the SQL version (and "bitness"). You have to use the "Get Registry Key Value..." script function to see if the specific SQL version is installed (32- and 64-bit versions).
For example, you have to scan the registry for:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2005\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SHAREPOINT\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SOPHOS\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SHAREPOINT\Setup Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Setup Edition
(...and more...)
Friedrich