We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

snowman
Posts: 2
Joined: Wed Nov 07, 2012 1:06 am

Creating installer for SDK

First of all as this is my first post in this forum, I would like t thank u for such a brilliant product. we have tried different programs before, but for most cases where sample packaging was top requirement all other products seemed to be complex and Advanced installer is the only program we are really satisfied with.

now as far as my question is concerned, our company develops back-end servers based on Microsoft .NET framework so we decided to create installer for our SDK which will include severl Visual Studio project templates and item templates as well. those templates will have references of some of our SDK DLL s installed on clients computer using your installer. the problem we are facing with are.

developer machines might be x64 or in some cases it might be x32 as well so in order to be able to directly add references to our SDK using visual studios' add refference dialog window those DLL s need to be added inside windows registry. so here is firs problem.
  • how can we detect Visual Studio installation?
    how to get installed net framework version so that windows registry entries are in right place after installation?
according to MSDN documentation http://msdn.microsoft.com/en-us/library ... 10%29.aspx there are several places where we need to add registry entries to enable global visibility of SDK assemblies so that developers do not have to brows for directory to add them to their project

Those registry entries are

For a 32-bit operating system, add one of the following registry keys.
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\.NETFramework\VersionMinimum\AssemblyFoldersEx\MyAssemblies]@="AssemblyLocation"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\VersionMinimum\AssemblyFoldersEx\MyAssemblies]@="AssemblyLocation"


For a 64-bit operating system, add one of the following registry keys in a 32-bit registry hive.
[HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\VersionMinimum\AssemblyFoldersEx\MyAssemblies]@="AssemblyLocation"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\VersionMinimum\AssemblyFoldersEx\MyAssemblies]@="AssemblyLocation"



we can not really understand how to add those registry entries using Advanced installer? registry hive hierarchy and the way Advanced installer allows developers to add registry values are not clear for us.

can anyone assist us with this problem and how to solve our issues?
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Creating installer for SDK

Hi and welcome to our forums,

Thank you for your kind words, we are really happy to see our simple UI works as designed, i.e. easy and efficient.
how can we detect Visual Studio installation?
You can make a simple registry search and retrieve the install folder from there, in our Search page. For example for VS 2010 you have this registry value
storing the install path SOFTWARE\Microsoft\VisualStudio\10.0\InstallDir.

The "Type" of the search you define should be "The value contains a path to a directory".

For VS 2012 the registry path is SOFTWARE\Microsoft\VisualStudio\11.0\InstallDir.
how to get installed net framework version so that windows registry entries are in right place after installation?
You can also make registry searches for this too. To see what registry you need to search you can temporarily add as prerequisites .NET framework from our list.
Then go to Install Conditions tab for each prerequisite, there you will see a set of registry entries which can help you track each version of .NET framework.

Regarding the registry entries for making your SDK visible, you don't need to worry about "Wow6432Node" key, this is automatically added by the setup package
on 64-bit machines. So you just need to create entries under the normal registry path as you would for a 32 bit machine and when the installer runs on a 64 bit machine
the registry entries will be redirected automatically under "Wow6432Node".

Best regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
snowman
Posts: 2
Joined: Wed Nov 07, 2012 1:06 am

Re: Creating installer for SDK

Thank you for your replay as information regarding x64 installation was very valuable for us. but there are still some questions we hope to get answers for. for example how to add those registry keys in hierarchy? does this mean we have to add each individual hierarchy level and finally add actual value?

U mentioned using registry to detect visual studio installation, can you provide more detailed information regarding how to use that feature of Advanced installer and provide us with link for this kind of tasks?

and there is option to create x32 and x64 or mixed mode installers does this mean if we want to create x64 or Mixed mode installers to have registry entries automatically added to the registry we have to create mixed mode installer?
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Creating installer for SDK

Hi,
for example how to add those registry keys in hierarchy? does this mean we have to add each individual hierarchy level and finally add actual value?
Yes you need the entire hierarchy, the installer will only create the registry values if those registry keys already exist on the machine. You can also import a .reg file in Advanced Installer, so if you have that you can speed up things a little bit.
U mentioned using registry to detect visual studio installation, can you provide more detailed information regarding how to use that feature of Advanced installer and provide us with link for this kind of tasks?
I have an example with a file search (step 6 from the tutorial). You can change that easily and have a registry search.
and there is option to create x32 and x64 or mixed mode installers does this mean if we want to create x64 or Mixed mode installers to have registry entries automatically added to the registry we have to create mixed mode installer?
Now, you should leave this with the default set by Advanced Installer, i.e 32 bit package. This package will behave exactly as I said above, i.e. will create the registry entries in the mentioned paths on 32 and 64 bit machines.

Best regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”