Often, right after a deploy, Visual Studio "has encountered a problem" and dies. The build/deploy work, the board starts up executing the new program. The crash box pops up at the moment of reset: Box comes up, normal boot delay for Netduino, program is running.
Sometimes it doesn't crash.
My environment is UbuntuLucid + VirtualBox + WindowsXPSP3 + VSC#2010Express + NetduinoMini on RS232.
Is this seen by others? Any hints? Thanks.
PS: Hope the Mono implementation is coming along...
Visual Studio dies after deploy
Started by teachop, Dec 27 2010 12:50 PM
6 replies to this topic
#2
bill.french
-
- Members
-
- 260 posts
Advanced Member
- LocationPrinceton, NJ
Posted 27 December 2010 - 02:21 PM
I had this issue, but it seemed to only be for certain projects. Strangely, simpler ones seemed to die more consistently. The issue for me has gone away, but i'm not sure if it's because my projects have gotten more complex, or the firmware updates. Are you up-to-date on your firmware?
#3
teachop
-
- Members
-
- 44 posts
Advanced Member
Posted 27 December 2010 - 03:20 PM
Are you up-to-date on your firmware?
MFDeploy SolutionReleaseInfo.SolutionVersion = 4.1.0.5 which I think is up to date. The program is tiny, a variation on the example LED blinker.
#4
Chris Seto
-
- Members
-
- 405 posts
Advanced Member
Posted 27 December 2010 - 04:19 PM
I get this issue as well. Usually happens the first time I try to do anything with VS in that session (Session == from the time I start my computer in the morning, to when I turn it off later)
#5
Cuno
-
- Members
-
- 144 posts
Advanced Member
- LocationZürich / Switzerland
Posted 27 December 2010 - 09:45 PM
Same for me, on a Windows XP machine with Visual Studio 2010. Deployment seems to work, but Visual Studio crashes and I have to restart it. After that, everything works fine, until I start up Windows XP again the next day.
#6
teachop
-
- Members
-
- 44 posts
Advanced Member
Posted 28 December 2010 - 10:49 AM
I did experiments with restarting XP. In my case the bug is more random, and occurs at other times, not just the first deploy after booting.
The message "not in an initialized state" timing predicts the impending crash. It hangs on for a while (seconds) in the cases where a crash will happen. When it is quick, it doesn't. Is that a hint to tracking it down or just an effect?
#7
Martin Ayotte
-
- Members
-
- 15 posts
Member
Posted 25 November 2012 - 02:27 AM
The problem probably still there : for me, VS2010 crash after deploy, approx. 1 time out of 5 deploys, although it shown that deploy been successful and my netduino deployment is effectively working. It is probably caused by bad cleanup of USB port.
I'm using netduino plus with firmware 4.2.0.1, and I'm running this environment under a Vista VM in VirtualBox 4.2.4 with USB filter from host Unbuntu 11.04.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
