Group: StrataFrame Developers
Posts: 6.6K,
Visits: 6.9K
|
Eric:
Do you have the keys I mentioned in the HKEY_LOCAL_MACHINE? This is where the install looks and where VS places these keys. If you just create the keys, the install will let you choose VS 2012, but you may have some downstream issues. These keys that we test on are not something that we created, but rather VS2012. We rely on these keys to know where and how to put SF templates for items as well as projects.
For a 64-bit machine, these are the values that we need: Read Registry Key HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\11.0\VSTemplate\Item\UserFolder into ITEMTEMPLATESFOLDER2012 Read Registry Key HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\11.0\VSTemplate\Project\UserFolder into PROJECTTEMPLATESFOLDER2012
For a 32-bit machine, these are the values that we need Read Registry Key HKLM\SOFTWARE\Microsoft\VisualStudio\11.0\VSTemplate\Item\UserFolder into ITEMTEMPLATESFOLDER2012 Read Registry Key HKLM\SOFTWARE\Microsoft\VisualStudio\11.0\VSTemplate\Project\UserFolder into PROJECTTEMPLATESFOLDER2012
You can see that we read these values into variables that are passed over to the install process. This tells the install where to place the item and project templates. Honestly, I don't think I have ever seen this fail before, so I know that it has something to do with the environment or the install. Not sure which. I have a clean VM setup and tested this starting from scratch to make sure something wasn't missed. Those keys were created by the install. I have another scenario here I am going to test with an upgraded OS instead of a clean install to see if that makes any difference, but if those keys don't exist, then there isn't much I can do other than tell you that we rely on the as part of the VS integration process.
|