[Solved] Odd behaviour in Visual Studio
-
I have 3 installs of Visual Studio 2012 Pro. One on my main PC, one on my laptop and one on the ultrabook received as part of the competition. The application being developed will run on the PC and the Laptop in Debug mode quite happily. On the ultrabook it throws Invalid Operation exception due to cross threaded calls. The project is identical on all 3 machines, as the code is pulled down from a central source control server. When compiled (default Any CPU etc. options) and run the exe directly, the application runs fine on all 3. There are no background workers etc. there is only the single thread. I have not changed any settings on any of them, they are all the stock install and on first run of VS, the C# environment was selected as layout choice. How the hell can I get to the bottom of this one? Any ideas? :confused:
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
I have 3 installs of Visual Studio 2012 Pro. One on my main PC, one on my laptop and one on the ultrabook received as part of the competition. The application being developed will run on the PC and the Laptop in Debug mode quite happily. On the ultrabook it throws Invalid Operation exception due to cross threaded calls. The project is identical on all 3 machines, as the code is pulled down from a central source control server. When compiled (default Any CPU etc. options) and run the exe directly, the application runs fine on all 3. There are no background workers etc. there is only the single thread. I have not changed any settings on any of them, they are all the stock install and on first run of VS, the C# environment was selected as layout choice. How the hell can I get to the bottom of this one? Any ideas? :confused:
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
What OS are you running them on? Is it W8 fully installed?
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
What OS are you running them on? Is it W8 fully installed?
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
They are all running Windows 8 Pro.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
I suspect it's the sensors. I get this in my sensor code, and it's straightforward enough to marshal back to the primary thread.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
I suspect it's the sensors. I get this in my sensor code, and it's straightforward enough to marshal back to the primary thread.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
That what I was thinking, but the part that confuses me is that the EXE runs fine directly. I'll do some more tweaking and tidying up and see how it goes. Cheers Pete.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
How are you getting on? I've just spent two hours debugging an issue with the Toast notifications that turns out that I had 2 identifiers the wrong way round.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
How are you getting on? I've just spent two hours debugging an issue with the Toast notifications that turns out that I had 2 identifiers the wrong way round.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
I'm just back from playing footy. I'm starved, tired and brain dead. Don't think last nights booze helped either! I'm going to get back into things tomorrow.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Let me know if you want my updates. I've got the Toast stuff working now as well.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
I have 3 installs of Visual Studio 2012 Pro. One on my main PC, one on my laptop and one on the ultrabook received as part of the competition. The application being developed will run on the PC and the Laptop in Debug mode quite happily. On the ultrabook it throws Invalid Operation exception due to cross threaded calls. The project is identical on all 3 machines, as the code is pulled down from a central source control server. When compiled (default Any CPU etc. options) and run the exe directly, the application runs fine on all 3. There are no background workers etc. there is only the single thread. I have not changed any settings on any of them, they are all the stock install and on first run of VS, the C# environment was selected as layout choice. How the hell can I get to the bottom of this one? Any ideas? :confused:
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
I would check that you have the needed framework on that ultrabook as you have in the solution are complete. May be a missing some contents in the framework on the ultrabook. Easiest test is to reinstall the updated framework bundles and try it again. Could also be a disconnect in the references in the setup of the ultrabook visual studio session.
-
I would check that you have the needed framework on that ultrabook as you have in the solution are complete. May be a missing some contents in the framework on the ultrabook. Easiest test is to reinstall the updated framework bundles and try it again. Could also be a disconnect in the references in the setup of the ultrabook visual studio session.
The problem was in fact related to the sensor on the ultrabook. As they existed on the ultrabook, when they were running they caused cross thread issues, on the other machines they didn't exist so didn't trigger any cross thread calls.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject