RE: Starting VS IDE with WSH script causes catastrophic process fa
- From: Chris <Chris F@xxxxxxxxxxxxxxx>
- Date: Thu, 4 Dec 2008 17:40:06 -0800
Hi Hongye,
Once I used your script, both problems were solved. Thanks for your help!
--
Chris
""Hongye Sun [MSFT]"" wrote:
Hi Chris,.
You are welcome to Microsoft Newsgroup Service. My name is Hongye Sun and
it is my pleasure to work with you on this issue.
In this post, we have two issues.
1. How to pass environment variables to Visual Studio
2. Why Visual Studio crashes or hangs when opening Test View window
For the #1 issue, there is another piece of vbscript, which has been tested
successfully in our lab.
-------------------------
set oShell=createobject("WScript.Shell")
set envSystem = oshell.Environment("process")
var = "UnitTestingValues"
envSystem.item(var) = "C:\Utils\MyDir\UnitTestingValues.xml"
oShell.Run """C:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE\devenv.exe""", , True
-------------------------
The vbscript you provided cannot pass environment variable to process. The
reason is
-------------------------
objConfig.EnvironmentVariables("UnitTestingValues") =
"C:\Utils\MyDir\UnitTestingValues.xml"
-------------------------
Since EnvironmentVariables is a string array, and VBScript syntax doesn't
allow set a variable by this way. Instead, we should use
-------------------------
objConfig.EnvironmentVariables =
Array("UnitTestingValues=C:\Utils\MyDir\UnitTestingValues.xml")
-------------------------
However, in this way, all the other environment variables will be missed.
For the #2 issue, can you do some simple tests to help us narrow down the
problem.
1. Try the script in solution to #1 issue. It may fix the #2 issue as well.
2. If step 1 still fails, change the "UnitTestingValues" to the path as
same as system environment variable.
3. If step 2 still fails, run the script again, create a new test project
and view Test View window again.
4. Delete system environment variable "UnitTestingValues", and open Visual
Studio directly. Check if it crashes again.
If all the above steps not working, can you specify "/log" option after
devenv.exe command. The script will be:
-------------------------
oShell.Run """C:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE\devenv.exe /log""", , True
-------------------------
It saves Visual Studio tracing info into
"%AppData%\Microsoft\VisualStudio\9.0\ActivityLog.xml". Please check the
xml file after Visual Studio crashes.
In addition, it will be very helpful if you can build a small reproduce
project and send it to us hongyes@xxxxxxxxxxxxxxxxxxxx, remove 'online.'.
We will take a deep look of it in our lab.
Please try the actions above and let us know the test results. In the
meanwhile, we will still perform research in our lab to check any other
possibilities of the crash issue.
Regards,
Hongye Sun (hongyes@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.
Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
- Follow-Ups:
- RE: Starting VS IDE with WSH script causes catastrophic process fa
- From: "Hongye Sun [MSFT]"
- RE: Starting VS IDE with WSH script causes catastrophic process fa
- References:
- Starting VS IDE with WSH script causes catastrophic process failur
- From: Chris
- RE: Starting VS IDE with WSH script causes catastrophic process failur
- From: "Hongye Sun [MSFT]"
- Starting VS IDE with WSH script causes catastrophic process failur
- Prev by Date: RE: ActiveDirectory and user page Access
- Next by Date: RE: Starting VS IDE with WSH script causes catastrophic process fa
- Previous by thread: RE: Starting VS IDE with WSH script causes catastrophic process failur
- Next by thread: RE: Starting VS IDE with WSH script causes catastrophic process fa
- Index(es):
Relevant Pages
|