Visual Studio 2010, I was able to view xaml in designer. Now every xaml I click, it gives me the exception and there is no info about what causes the exception. I tried reboot my PC, the issue still occurrs. I feel I must miss something? thanks
I installed visual studio service pack 1 and now the issue is resolved. thanks
Often when using custom complex styles I find the designer struggles to render the XAML regardless of the service pack. Something to keep in mind
Related
I am facing a very, very strange issue in Visual Studio 2015 RTM, while programming a Windows Forms Application.
My Program class, (entry-point-) Main method has a routine that checks if a certain configuration file exists in the current output folder, alerting an error and forcing an Environment.Exit(-1) if otherwise.
I have a UserControl I intend to add to a particular form and... when, in design time, I try to add the built component into it, this happens,
crashing the IDE with it.
Please notice that the message alert was created after a generic exception was caught, back at the entry point (the Log extension method does it).
I'm running a VS2015 RTM version, along with a fresh-from-update Resharper 9.1.3 and PowerTools. This issue has not happened in VS 2013 Premium.
Has anyone here faced something similar?
UPDATE
I just realized how confusing a code in a foreign language can be, so I'll try to explain it the best I can, updating the first image.
UPDATE(2)
It has happened in VS2013 Premium, running a 9.1.2 Resharper and PowerTools. Am I missing something here?
UPDATE(3)
This is not an answer: Catching exception in Main() method
It happens in design time, not in debug mode.
I'm getting the following error message
Cannot access a disposed object. Object name: 'MarshalingWindowFrame'.
This message came when I tried to load a SLN file into VS2013.
What is the reason?
I am using VS2013 Ultimate with Update 4 on Windows8.1 pro x64 bit OS (8GB RAM, 500GB HDD)
If you get that when opening a solution, either an addon is bugging out or (worse, but less likely) you found a bug in VS itself. Try safe mode and see if that helps.
If however you get the error when opening a form rather than the solution itself (remember opening a solution loads the various forms), there's a bug in an user control that's trying to access a disposed object. Remember that user controls run as binaries when hosted in VS, so make sure you put actual code inside guards that require you not to be in design mode.
Was that project created in the earlier versions or in the Visual Studio 2013 Preview? Because, if you update this project from Visual Studio 2013 Preview, you have to check the update procedure (http://blogs.msdn.com/b/lightswitch/archive/2013/08/12/upgrading-your-lightswitch-projects-raghuveer-gopalakrishnan.aspx) first, perhaps it can give some hints why this happens.
We just upgraded to visual studio 2010 RC1 and all of a sudden our controls inside tabcontainer disappeared from the designer file.
Actually, it all seemed good in the beginning, the project compiled nicely, but as soon as we did any change in the markup of a page and build the code for the controls inside the tabcontainer disappeared and we got errormessages like so
"Error 3 The name 'ddlPeriodicityStartInMonth' does not exist in the current context "
Does anyone know if any changes are made to tabcontainer to visual studio 2010 or if this just is a bug?
Thanks in advance.
Found this one also.
Workaround: Missing Declarations for Controls in Designer File
I had the same problem.
Check out the following link:
Microsoft Connect - Bug in generating the designer.cs file in VS2010
Hope it helps.
This has been driving me crazy for months. I have a multiple projects that compile without errors. If I start copying and pasting controls (or even just plain 'p' tags) the designer will fail 1/2 the time with the error "the method or operation is not implemented". The complexity of the page doesn't matter. The 'solution' is to delete the designer file, exit visual studio, open visual studio and convert the offending aspx file to a 'web application' to regenerate the designer file.
This is a really annoying. I can't find any fixes on Google. Is there a way to disable the automatic designer file? Make it so it only generates on a 'build' command and not fail everytime I'm laying out a aspx page?
Thanks
To find the fix for the issue you would need to find the cause of the issue. It might be possible to get more information on what is causing the issue if you attach a debugger to Visual Studio. This could be done by following these steps:
Open two instances of visual studio (run as administrator)
In one, open your project and get to a point right before the issue occurs
Attach the other instance of Visual Studio to the one with your project (Tools -> Attach to Process)
Perform the steps to reproduce the issue.
Note that to actually catch the exception you will need to change a few debugging options. First you would need to make sure that the Just My Code check box is unchecked in the General debugging options in Visual Studio. The second is on the exceptions dialog you will need to catch thrown exceptions. The exception dialog is under the Debug menu in Visual Studio.
A few times a day my VS2008 SP1 freezes if I edit XAML code. It just got stuck and I have to kill the process.
It seems to be a problem with the IntelliSense or the spell-checking or whatever process is going on while I edit code.
The problem is very apparent if I copy+paste some code. Even if it is just one word. Many times VS2008 adds some additional commands in the code and messes things up completely.
This never happened with C# code only with XAML it does get stuck.
One more thing: It seems the problem only occurs when I edit control templates. I added a few control templates from the MSDN pages to my project. When I edit them - even doing simple things like changing brush colors - Visual Studio freezes (sometimes). So it seems it's not a general XAML problem it happens with control templates only.
You could try this update: Installing DExplorer after VS 2008 breaks xaml intellisense
EDIT: You could try closing the Properties window when editing XAML, it helped me before with ASP.NET.
Some other links:
Xaml Editor Crashes after Visual Studio 2008 SP1
Using the Source Code Editor for XAML in Visual Studio
After having this problem and hunting around on the interwebs I found this vsnet-crashes-when-editing-xaml
Which said, in summary, if you edit a xaml resource while something that uses said resource is open in a designer, then you'll be sorry.
So you can avoid the problem by
Closing the other designer windows;
Installing hotfix KB958017.