A few months ago I imported the HTML5/CSS3 update into Visual Web Developer 2010, and after the update ended I could not open CSS files in the Visual Studio editor. When I try I get the error:
The operation could not be completed. Unspecified error
Here is a image of the error:
I have opened the file successfully in Notepad++, but can be a hassle to do that every time I need to edit CSS or want to debug and switch windows.
Why is this happening? What can I do about it? Is my CSS editor broken for good?
Turns out since I had installed the Web Standards Update for Visual Studio 2010 S1, it didn't work. All I had to do was open the installer again and repair the update. I can now open .css files again!
EDIT
Useful link I used: http://social.msdn.microsoft.com/Forums/en/vssetup/thread/e505875a-0b74-4d46-987b-e376f958b9bc
Related
I try to edit an axml file in Visual Studio, because drag and drop doesn't work in Xamarin Studio. But when I open my axml file, it's loading forever.
I've been waiting for more than 10 minutes, but it is still loading. When I restart VS I can open the axml file without any problems.
The same applies for all my other axml files (in other projects).
Does anyone knows how to fix this?
I'm using the newest stable version(cycle 8) of Xamarin btw.
EDIT:
I'm using Visual Studio Community 2015 Version 14.0.25425.01 Update 3 and I've got all the latest updates installed.
More detailed explanation:
I open my project in Visual Studio
I open my foo_bar.axml file
I switch from the Designer tab to the Source tab
I remove the android:background="blablabla" attribute
I switch from the Source tab to the Designer tab
The Designer tab is loading forever
AND
I open my project in Visual Studio
I open my foo_bar.axml file
I make some changes
I close the foo_bar.axml file
I reopen the foo_bar.axml file
the foo_bar.axml file is loading forever
NOTE:
The problem doesn't happen when I change the android:text="blablabla" attribute at step 4 and when I change some other attributes it also doesn't happen, so it is specific to just some attributes.
According to a forumer at Xamarin Forums, it has something to do with Cycle 8's AXML Designer not being able to render using the newest API.
But even in Cycle 8 when I choose to compile under Android 6.0 instead of 7.0 in the project's properties, the designer is still wonky as it is. Switch between "Designer" and "Source" on one .axml file and the designer still loads until Harambe cometh.
Therefore, your best bet is to downgrade Xamarin Studio to Cycle 7, and you can finally get the AXML Designer as working as before.
Until Cycle 9 or an incremental update/hotfix of Cycle 8 comes about, this is the way to go for now.
You can download and install the previous cycle in the link below:
https://store.xamarin.com/account/my/subscription/downloads#cycle7
For your own interest, you can read more about the aforementioned forum thread below:
https://forums.xamarin.com/discussion/77992/axml-layout-designer-inside-visual-studio-keeps-loading-forever
This happened to me also. Then I realised I hadn't opened Visual Studio in Admin mode. After I did, everything was fine.
Open the visual studio as admin and it loads perfectly. All the best.
I get a blank security warning popup window when trying to open a website, in Visual Studio 2015 Community Edition. It worked on my other computer in the same environment.
I moves the files to a new fresh computer and I get this window.
Here's a screenshot:
Nothing is clickable, even what where the buttons should be. Visual Studio is just frozen, can't even close the IDE nor the popup window. It doesn't happen to Web Projects, only websites.
Any idea how to solve this?
I got the same issue. Just fixed it. In my case it was entity ".tt" files fault. I guess for some reason VS 2015 does not recognize ".tt" extension. I've just deleted these files and run website (not web application) successfully
The .tt files are needed if using Entity Framework.
Here is my workaround that worked in two cases of the blank security warning. Rename the files with .tt extension to .tt.old.
Open the project (it will not compile, so don't try)
Save and close the project
Rename the .tt.old files back to their original names
Open the project again, this time the warning will have content and will be clickable.
I have installation of VS 2010 SP1 with T4 editing and modelig tools installed problem is that suddenly all icons fro .tt files gone and it has unknown icon. when I open it in VS simple text editor is opened not tengable nothing is working reinstalling extention did not fix the problem. I have notification when I open vs that there are extension updates available and it says that modeling and editing tools update is available. but when I click download button nothing happens. Pleas someone recommend something my projects heavily depend on .tt.
I found that there was a problem with Visual Studio installation so After clean reinstall everything works perfect
As the title says, my Visual Studio 2010 SP1, running on Windows 7 x64, is crashing whenever I try to open a .html, .aspx, .cshtml, etc. file. I noticed this problem some weeks ago. Since then, when I open one of these kinds of files, it opens, freezes for a few seconds and then crashes. I tried using the repair function provided with the installer, but it didn't work. The only solution right now is to reinstall the os, but I don't feel like doing such thing.
Has anyone else encountered this kind of problem? Thank you!
I've been having this problem when using the default Web Form Editor and still haven't found a solution that works. I haven't a clue what's causing it, and the only plugin I have is Resharper.
I solved it temporarily by right-clicking the ASPX file, clicking Open with and choosing HTML Editor as the Default editor. Seems to be a problem with the Web Form Editor for a certain kind of files.
Visual Studio 2008 has been very stable for months on my computer.
This morning when I double-click on any .xaml file to open it, or even click on the tab of an already opened .xaml file, Visual Studio says "initializing toolbar" in the status bar and then 20 seconds later fully closes the whole application without any error message.
Other files (e.g. .cs class files) I can open fine.
Has anyone experience this or know what I could check/change to be able to use Visual Studio to edit .xaml files again?
MORE INFO: I can also create a new project and create and edit .xaml files fine.
MORE INFO: I can edit .xaml files in other modules (projects) fine.
MORE INFO: Everytime it crashes, this event is registered:
.NET Runtime version 2.0.50727.3053 - Fatal Error in executable module (72555E00) (80131506).
(odd since I have .NET framework 3.5 installed)
MORE INFO: It is only in one module (project) that .xaml files cause Visual Studio to crash. Even creating a new UserControl in that module crashes Visual Studio.
I get this occasionally (with .xaml and .resx files) and find that if I delete the solutions .suo file things work fine again.
[The suo file just contains per user settings like recently opened files etc so it's nothing important and will just be recreated when you next open the solution.]
I've been getting the same issue whenever I try to access project settings for a C# project.
Found additional information about this:
Here: http://blog.fryhard.com/archive/2008/11/26/visual-studio-2008-closes-at-build-outlook-2007-add-in.aspx
And here: http://social.msdn.microsoft.com/Forums/en-US/vsto/thread/99e124d0-c5d7-49c0-b1dd-71328f9a6571/
Apparently it's a bug in the core CLR engine that causes the entire CLR to crash if certain types of assemblies are loaded in a certain order.
Most of the time it appears to be directly related to the Visual Studio add-in called PowerCommands - uninstalling PowerCommands will make the problem go away.
And (we hope) it's supposed to be fixed for .Net 4.
This sounds very similar to the issue I had when I first installed VS 2008. Unfortunately, after hours of research, I ended up reinstalling the IDE (with my fingers crossed). No problems since then, but it's obviously not the most enjoyable way to solve the problem.
What is likely happening here is that one of the controls referenced directly on indirectly in your designer is stack overflowing during the designer process. Because the designer is hosted in process a stack overflow by one of the components will take down the designer and VS.
Try attaching a debugger to VS, break on first chance StackOverflow Exceptions and open the designer.