VS2012 and Existing WPF Solutions
-
I tried to open a WPF app at work with VS2010, and none of the forms display (it says there was an error and I have to reopen the designer). The only thing that's different on the system is Friday's addition of VS2012. Has anyone else seen something similar? One of the errors is "Unexpected record in Baml stream. Trying to add to Setter which is not a collection or has a TypeConverter." EDIT: Confirmed problem - when I open the project up in VS2012, the form is displayed as expected. With VS2010, the designer chokes and refuses to display it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997If it's any consolation, VS2010 decided it didn't like my Winforms app this morning and it took me about an hour to "persuade" it to show the main form in the designer. :mad:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
It looks like we're going to have to uninstall it. Something similar happened to me at home as well in one of my own WPF projects.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997The only WPF fix that was in there that was of any real interest was the solution to the airspace issue, and as we've redesigned our interfaces to avoid this, it's all moot anyway.
*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 tried to open a WPF app at work with VS2010, and none of the forms display (it says there was an error and I have to reopen the designer). The only thing that's different on the system is Friday's addition of VS2012. Has anyone else seen something similar? One of the errors is "Unexpected record in Baml stream. Trying to add to Setter which is not a collection or has a TypeConverter." EDIT: Confirmed problem - when I open the project up in VS2012, the form is displayed as expected. With VS2010, the designer chokes and refuses to display it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
It looks like we're going to have to uninstall it. Something similar happened to me at home as well in one of my own WPF projects.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997I've been planning on pulling 2012 down this coming weekend. I suppose your issues mean I should be safer and use a VM for this instead of a side-by-side install with 2010 on my main development machine.
I wasn't, now I am, then I won't be anymore.
-
One thing to check is if the references of any of the assemblies now point to the framework version 4.5 instead of 4? We had that problem when moving from 3.5 to 4.0...
JimmeP wrote:
One thing to check is if the references of any of the assemblies now point to the framework version 4.5 instead of 4? We had that problem when moving from 3.5 to 4.0...
How could installing VS2012 possibly change the solutions themselves? If the solution is set to use .Net 4 (or earlier), VS2012 has no business changing it until I tell it to. Besides, the problem was discovered before even firing up VS2012 for the first time, and in a copied version of the solution.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I tried to open a WPF app at work with VS2010, and none of the forms display (it says there was an error and I have to reopen the designer). The only thing that's different on the system is Friday's addition of VS2012. Has anyone else seen something similar? One of the errors is "Unexpected record in Baml stream. Trying to add to Setter which is not a collection or has a TypeConverter." EDIT: Confirmed problem - when I open the project up in VS2012, the form is displayed as expected. With VS2010, the designer chokes and refuses to display it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Just to check - your VS2010 installation does have SP1 installed doesn't it?
*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
-
Just to check - your VS2010 installation does have SP1 installed doesn't it?
*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
Oh yeah - that was the first thing I checked... I reported the bug, but I'm not expecting much from MS Connect - they'll probably ask me what I had for breakfast... or what color my car is...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
JimmeP wrote:
One thing to check is if the references of any of the assemblies now point to the framework version 4.5 instead of 4? We had that problem when moving from 3.5 to 4.0...
How could installing VS2012 possibly change the solutions themselves? If the solution is set to use .Net 4 (or earlier), VS2012 has no business changing it until I tell it to. Besides, the problem was discovered before even firing up VS2012 for the first time, and in a copied version of the solution.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
How could installing VS2012 possibly change the solutions themselves? If the solution is set to use .Net 4 (or earlier), VS2012 has no business changing it until I tell it to.
"Madness? This is MICROSOFT!!" :D For some reason, that just came to me.
-
Oh yeah - that was the first thing I checked... I reported the bug, but I'm not expecting much from MS Connect - they'll probably ask me what I had for breakfast... or what color my car is...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
Oh yeah - that was the first thing I checked...
Given that you'd installed VS2012, I would have thought the first thing you'd have checked was that you had enough ammo to hand. After all, if you're going to shoot yourself in the foot, you might as well do it in style.
*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
-
John Simmons / outlaw programmer wrote:
How could installing VS2012 possibly change the solutions themselves? If the solution is set to use .Net 4 (or earlier), VS2012 has no business changing it until I tell it to.
"Madness? This is MICROSOFT!!" :D For some reason, that just came to me.
I suppose that's true - afterall, they removed the Start button from Windows...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I tried to open a WPF app at work with VS2010, and none of the forms display (it says there was an error and I have to reopen the designer). The only thing that's different on the system is Friday's addition of VS2012. Has anyone else seen something similar? One of the errors is "Unexpected record in Baml stream. Trying to add to Setter which is not a collection or has a TypeConverter." EDIT: Confirmed problem - when I open the project up in VS2012, the form is displayed as expected. With VS2010, the designer chokes and refuses to display it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997If you plan to continue developing for .NET 4, you really shouldn't use VS2012. The reason I say this is because of this[^] post. For those who don't want to read it, .NET 4.5 is an in place upgrade to .NET 4. In doing this, there are fixes to the .NET 4 binaries that mean that your application won't see bugs on machines with 4.5 that may well exist on machines with .NET 4 binaries installed. This could well lead to hidden bugs in your application.
*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
-
John Simmons / outlaw programmer wrote:
Oh yeah - that was the first thing I checked...
Given that you'd installed VS2012, I would have thought the first thing you'd have checked was that you had enough ammo to hand. After all, if you're going to shoot yourself in the foot, you might as well do it in style.
*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 purged it from my work system. :/
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
If you plan to continue developing for .NET 4, you really shouldn't use VS2012. The reason I say this is because of this[^] post. For those who don't want to read it, .NET 4.5 is an in place upgrade to .NET 4. In doing this, there are fixes to the .NET 4 binaries that mean that your application won't see bugs on machines with 4.5 that may well exist on machines with .NET 4 binaries installed. This could well lead to hidden bugs in your application.
*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
Holy crap on a cracker...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Holy crap on a cracker...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Possibly the best description I've read of it.
*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
-
Possibly the best description I've read of it.
*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 can't claim ownership of the phrase, and must thank Penny on Big Bang Theory (from the episode where Sheldon got a groupie, and Penny walked in on her giving Sheldon a pedicure).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
JimmeP wrote:
One thing to check is if the references of any of the assemblies now point to the framework version 4.5 instead of 4? We had that problem when moving from 3.5 to 4.0...
How could installing VS2012 possibly change the solutions themselves? If the solution is set to use .Net 4 (or earlier), VS2012 has no business changing it until I tell it to. Besides, the problem was discovered before even firing up VS2012 for the first time, and in a copied version of the solution.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997You do know that the .Net 4.5 BCL does NOT co-exist with 4.0. It replaces the 4.0 BCL when it installs! The 4.5 BCL installs with VS 2012.
-
I can't claim ownership of the phrase, and must thank Penny on Big Bang Theory (from the episode where Sheldon got a groupie, and Penny walked in on her giving Sheldon a pedicure).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997That's where I heard it before. I can't believe I didn't make the connection.
*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
-
If you plan to continue developing for .NET 4, you really shouldn't use VS2012. The reason I say this is because of this[^] post. For those who don't want to read it, .NET 4.5 is an in place upgrade to .NET 4. In doing this, there are fixes to the .NET 4 binaries that mean that your application won't see bugs on machines with 4.5 that may well exist on machines with .NET 4 binaries installed. This could well lead to hidden bugs in your application.
*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
So I guess it follows that if you develop a 4.0 app with VS2012, and someone installs it on their .Net 4.0 system, and they're forced to upgrade .Net 4.0, it could possibly break all of the older .Net 4-reliant apps on their system. How the f*ck did this one get by Microsoft "quality control"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
So I guess it follows that if you develop a 4.0 app with VS2012, and someone installs it on their .Net 4.0 system, and they're forced to upgrade .Net 4.0, it could possibly break all of the older .Net 4-reliant apps on their system. How the f*ck did this one get by Microsoft "quality control"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
So I guess it follows that if you develop a 4.0 app with VS2012, and someone installs it on their .Net 4.0 system, and they're forced to upgrade .Net 4.0, it could possibly break all of the older .Net 4-reliant apps on their system.
Not quite. They'd have to install .NET 4.5 to get the fixed version that matches your system. If they still use original .NET 4, there could be good old fashioned bugs in there that won't manifest on your system. Oh, and the fact of upgrading their system to 4.5 could end up breaking another .NET 4 application which has a workround that fixes one of the bugs.
John Simmons / outlaw programmer wrote:
How the f*ck did this one get by Microsoft "quality control"?
Asked and answered there mate.
*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've been planning on pulling 2012 down this coming weekend. I suppose your issues mean I should be safer and use a VM for this instead of a side-by-side install with 2010 on my main development machine.
I wasn't, now I am, then I won't be anymore.
Or install VS2012 FIRST, then install VS2010
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
