|
That designer not finding the namespace is still there, but I have logged it for 2017 and it's been triaged to "Under Investigation". I wonder if anyone bothered logging it before?
Immanentize the Eschaton!
|
|
|
|
|
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.
|
|
|
|
|
As soon as I overcome the complete and utter lack of space on the machine...
|
|
|
|
|
For that reason I had to reinstall my PC.
|
|
|
|
|
What about a spring clean. I use CCleaner. It just works! ![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
 it did take lots of disk spaces, I didn't select all the options during installation, and it took about 42GB of disk spaces.
Bryian Tan
|
|
|
|
|
Or to put it another way: until you get a new machine or hell freezes over (whichever happens first!) 
__________________
Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now.
© 2009, Rex Hammock
|
|
|
|
|
Remember the good old days when we were offered a choice of which bits to install? Most of the clutter that came with VS2013/15 was of absolutely no interest (to me at least).
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
