Talk:Viewer 2 Microsoft Windows Builds
A few style guidelines
- The person who is following these instructions for the first time may know little or nothing about VS2010. Steps should be kept simple and explained in well written English, not in a succinct description that an experienced person would be able to follow.
- If there is more than one way to do something only describe one of those ways. The philosophy at the start of this wiki page says, in part: to keep it brief, this page should only include steps we KNOW ARE NEEDED, not random hints.
- A path to, or a menu entry, should be in bold.
- A field you can change should be
- Instructions should apply to Visual Studio Express. If there is a small difference between Express and Pro assume the Pro user is experienced and can figure it out. Try to avoid instructions such as "If Express do this" or "If Pro do this".
- These instructions were written collaboratively and tested by the authors for correctness in all four combinations of XP/Windows 7 and Express/Pro. If you are going to make a change to these instructions it is strongly suggested you make sure your change works for all these combinations. As your development environment may not be this extensive you may want to recruit help from people in the #opensl IRC channel who are using other OS and compiler configurations.
- Also before making a change make sure it is not an issue with your local environment. Check with others to see if they are also having this issue.
- People following these instructions still "go wrong" and come to #opensl for help. If you have the skill to contribute to improving these instructions please consider having an IRC client open to #opensl to assist people.
- The full style guideline can be found here Style_Guide.
Jonathan Yap 07:09, 22 June 2012 (PDT)
- I rather want to have summary, such as, the table of configuration, needed commands without step-by-step instruction. Where to go such a article? If you don't plan to have that, we'd better have two page, one is your instruction, and other is "cheat sheet". -- Mako 08:54, 22 June 2012 (PDT)
- And by the wiki nature, I want every people post what they find without "filtering", accepting comments or suggestions on this wiki. If you have any comment about that, please write HERE, not IM to me, to share your thought to all the people who watch this wiki. Thanks. -- Mako 17:58, 22 June 2012 (PDT)
Mailing list discussions on compile errors, and more
Eliminate annoying IDE popup
If you are compiling with the IDE and keep getting a popup along the lines of "improve microsoft visual studio performance" Either
- To hide on XP or 2003 Server, right-click on the Task Bar | Select Properties | Select Taskbar tab | select Hide inactive icons | Click Customize | Set the Behavior for item "Improve Microsoft Visual Studio" to "Always hide".
- Follow the registry edit instructions just before "Was this information helpful?" at this link http://support.microsoft.com/kb/981741
Note: This second method did not work for me.
Jonathan Yap 8:43, 31 May 2011 (PDT)
Order of installing
I got errors during the installation of the directX SDK. the problems occured while it was installing the c++ Runtimes (which have already been installed before). So here is what i did to fix this:
- remove all 2010 installations
- install the DirectX SDK (June 2010) (that also installs the redistributable packages)
- Install the Visual C++ 2010 Express
- Install Windows SDK for Windows 7 and .NET Framework 4
- Run Microsoft Update
Gaia Clary 21:28, 8 Feb 2012 (CEST)
- FYI, This is what I find workable. If anyone stuck with the method on the article, try:
- Install Visual C++ 2010 Express (Web install) or Visual C++ 2010 Express (ISO)
- Install Windows SDK for Windows 7 and .NET Framework 4 (Web install) [Note: uncheck the Redistributable Package option to prevent installation failure] or Windows SDK for Windows 7 and .NET Framework 4 (ISO)
- Check if any Microsoft Visual C++ 2010 Redistributable Package is installed. If so, uninstall it (both x82/x64).
- Install DirectX SDK (June 2010)
- If you have default installed Direct X SDK, Microsoft Visual C++ 2010 Redistributable Package should have been installed as well.
- Run Microsoft Update, and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
- For Windows XP, use the provided link above. After then, use Microsoft Update on your start menu instead of default Windows Update.
- For Windows Vista and Windows 7, you can use the link above to add Microsoft Update feature to your Windows Update. "Microsoft Update" won't on menu, so you will have to use default Windows Update to update your Visual Studios.
- During the update cycles make sure you have picked up ”Microsoft Visual Studio 2010 Service Pack 1". If you haven't, get it from here (Web install) or here (ISO).
- -- Mako 21:34, 22 June 2012 (PDT)
Proposal: Move hints on this talk page to another page
Another hint. In general, we use the talk page to discuss the article itself, not for catch-all issue. See another talk pages and Project:Talk_Page_Guidelines for the references. Thus, you might want to create another page for hints, i.e. Viewer 2 Microsoft Windows Builds/Hint and move tips toward that page, and keep talk page open for people who want to say something about this article and maintenance style itself. -- Mako 06:44, 22 June 2012 (PDT)
- For a starter, I withdrew my two posts about tips under my namespace, User:Mako Nozaki/The Solutions Against The Viewer Troubles since currently I can't find no suitable place to post this article in main namespace. -- Mako 21:21, 22 June 2012 (PDT)
Should always re-install Windows operation systems before you start developing viewer?
Related to my previous post to the first topic, this instruction seems to anticipate your Windows "cleaned". However, we may have another projects, another environment, stuffs we can't delete. If we stuck in the middle, should we every time catch someone in the IRC or delete all the environment and start from installing operation systems again? I think wiki is for sharing informations so that people don't have to repeat the similar question on the mailing list or IRC. Just thought. -- Mako 17:40, 22 June 2012 (PDT)
Visual C++ 2010 Express
When using the Express version of Visual C++ 2010, the "autobuild configure" step will fail due to the changes from https://jira.secondlife.com/browse/OPEN-140. This is because the VSTool.exe application fails to return the expected value. You will receive an error message at the end of the configure step, but it is safe to ignore it. If you are not comfortable with that error message during the configure-process, simply replace the VSTool.exe file in indra/tools/vstool/VSTool.exe with ANY .exe file that returns 0.