Click here to Skip to main content
15,889,595 members

Survey Results

Will you upgrade to Visual Studio 2017?

Survey period: 13 Mar 2017 to 20 Mar 2017

Success to the Brave

OptionVotes% 
I've been running VS 2017 since pre-release1197.48
I'm already using VS 201734421.62
I will be moving to VS2017 ASAP16210.18
I'll upgrade soonish25415.96
I'll upgrade eventually47029.54
I can't see that I'll be upgrading1318.23
I don't use Visual Studio1116.98



 
GeneralRe: My old enemy, so here we meet again! Pin
W Balboos, GHB13-Mar-17 0:59
W Balboos, GHB13-Mar-17 0:59 
GeneralRe: My old enemy, so here we meet again! Pin
CDP180213-Mar-17 1:28
CDP180213-Mar-17 1:28 
GeneralRe: My old enemy, so here we meet again! Pin
CDP180213-Mar-17 2:41
CDP180213-Mar-17 2:41 
GeneralRe: My old enemy, so here we meet again! Pin
Nelek13-Mar-17 1:19
protectorNelek13-Mar-17 1:19 
GeneralRe: My old enemy, so here we meet again! Pin
CDP180213-Mar-17 1:34
CDP180213-Mar-17 1:34 
GeneralRe: My old enemy, so here we meet again! Pin
Nelek13-Mar-17 2:32
protectorNelek13-Mar-17 2:32 
GeneralRe: My old enemy, so here we meet again! Pin
Brady Kelly14-Mar-17 0:59
Brady Kelly14-Mar-17 0:59 
GeneralRe: My old enemy, so here we meet again! Pin
CDP180214-Mar-17 1:37
CDP180214-Mar-17 1:37 
I had an assembly which merrily mixed frontend and backend code. I had to put some application logic inbetween (something the original author of the code also never heard about), so I split the whole assembly in two. Except for renaming one single namespace, that was merely a matter of copying files from one project to another. All hell broke lose when I tried to compile the part with the WPF dialogs. It could not find hundreds of objects, most still in the same assembly and workspace as before. A second assembly which was built by the same hero depended on the code and now also does not compile anymore.

Now I have found a solution. Throw everything that uses XAML out of the project. Clean the solution and recompile your project. Now you should only have reasonable errors, like missing classes from the files you have just thrown out of the project. Then add the excluded files again, one by one, cleaning the solution and recompiling every time. If the chaos comes back in the middle of the way, it's back to square one. Congratulations if you have included all files again and it's still ok.

There was not a single error in the first assembly. It should just have compiled as it was, but I had to go through this entire procedure to get it working again. And now I have to do the same for the second assembly that depended on it.

Let Mickeysoft investigate as much as they want. Perhaps I will take a look at their bugware when they notice something.
The language is JavaScript. that of Mordor, which I will not utter here

This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.

"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."

If software development were a circus, we would all be the clowns.

GeneralOne Issue Pin
cjb11012-Mar-17 21:51
cjb11012-Mar-17 21:51 
GeneralRe: One Issue Pin
Zhivko Kabaivanov12-Mar-17 23:31
Zhivko Kabaivanov12-Mar-17 23:31 
GeneralRe: One Issue Pin
KarstenK13-Mar-17 0:32
mveKarstenK13-Mar-17 0:32 
GeneralRe: One Issue Pin
Bryian Tan13-Mar-17 2:50
professionalBryian Tan13-Mar-17 2:50 
GeneralRe: One Issue Pin
Jalapeno Bob13-Mar-17 4:33
professionalJalapeno Bob13-Mar-17 4:33 
GeneralRe: One Issue Pin
Herbie Mountjoy13-Mar-17 21:57
professionalHerbie Mountjoy13-Mar-17 21:57 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.