I'm wondering if there are any workarounds for this issue, as I am plagued by frequent crashes -- though it isn't clear whether the crashes are caused by Resharper, Xamarin Tools or the mixture of C# and F# projects.
When I restart Visual Studio and load a solution containing Xamarin Forms projects, the entire display locks up. After one to three minutes, I get a pop-up saying that an update for Xamarin for Visual Studio is available (Clicking on the pop-up has no effect, so I'm assuming this is a false positive). A few seconds after that, it attempts to connect to my Mac, which is often unsuccessful as I work on my laptop and that connection is only available when I'm at home.
Only when the connection to the Mac has failed am I able to interact with Visual Studio, and then, about 30% of the time, attempting to build, clean or rebulid simply results in a pop-up saying "The operation could not be completed". The only way to fix that is to restart Visual Studio, causing the whole grinding process to restart again.
Xamarin themselves have referred me to these forums. Obviously this is not a pure software question, so I'll try to distill this into specific answerable questions.
Is there a way to prevent the false positive that tells me a new version of Xamarin for Visual Studio is available when it clearly isn't?
Is there a setting that I can use in order to opt in to connecting to the Mac, rather than attempting to make a connection and killing startup time when I know in advance that the connection will not be made?
Has the build problem "This operation could not be completed" been reported anywhere? I haven't found any instances of this problem related to Xamarin or Resharper. But it is frequent.
Does this consistently happen? We've had this problem over the years, but it's gotten much better. Make sure all your machines are synced with the latest Stable update. If on Beta/Alpha, this is typical as we push builds often. The strange part is that you say it's trying to update Xamarin Studio, we actually don't ship Xamarin Studio for Windows anymore: https://www.xamarin.com/faq#xpq6. So it might be a good idea to uninstall a previous version of Xamarin Studio on Windows if it's there.
This is a good point. It's something that might need a small papercut bug filed. Feel free to log an issue here and I can coordinate the status: (https://bugzilla.xamarin.com/enter_bug.cgi?product=Visual%20Studio%20Extensions). In the past I've seen a couple ways around this. 1) Make a seperate .sln that might be called .Windows which will only load Windows native projects (Android, UWP, etc). This way the step is skipped completely. 2) You can simply unload the iOS project until you need to reload the project and work on the iOS side. However I do agree there should be a project property/IDE setting that should say "Start Xamarin Mac Agent on Startup".
That error is really vague. We would need to gather some logs(log files can be gathered from %LOCALAPPDATA%\Xamarin\Log or using Help->Xamarin). This operation could not be completed typically has an error/exception following it like This operation could not be completed: Invalid Pointer. So we would need to dig into logs here and see if we can get a Stack Trace when it happens. I would also try deleting your .suo in the .vs hidden folder of your project directory.
Several class wizard functions aren't working, most of which I don't need very badly, but not being able to add classes to MFC controls is a big problem. I have an MFC dialog project going on, and whenever I try to, say, add a function to a class I just get "The operation could not be completed"--not very helpful. If in the resource view I right-click on a dialog and select "Add Class..." nothing happens.
I have Microsoft Visual Studio 2005 w/SP1. I'm running WinXPHESP3 32-bit.
BTW, this project was imported from VS 6.0, so I've got a bunch of things lying around like AFX_MSG_MAP, which I'm starting to suspect is useless and maybe interfering.
Like I mentioned in comments, a repair didn't work, so I did a reinstall. That also had a few errors, but VS seems to work now. If I had to do it all over again, I might have tried reinstalling the SP1 first.
I have a very weird problem. In Visual Studio 2013 I working on an application for sorting and renaming files. It is not done yet, but I wanted to show it to some other people on another PC. I have tried almost every menu in every possible context but I simply can't find the publishing wizard or any other tool for that. Normally I should just do a right click on the project and have the option "Publish..." there, right? I have also tried the build menu. All I get is "Build", "Rebuild", "Clean" and "Code analysis". No option for publishing. Maybe I am just stupid and forgot to configure something? It seems like the word "publish" has completely vanished from the whole program. I have seen screenshots and in my VS the option is simply missing. Does anyone have an idea how to fix this?
I also tried adding an installer project, but then it just tells me that there was some kind of an error. No further information. Just "an error occured".
Any help will be appreciated! :)
Your application after build is in YourProject\bin\Release\ or YourProject\bin\Debug\ path.
I'm writing a project in Visual Basic 2008 Express Edition, which used to work completely fine until that moment, when I decided to install MS Chart Control in order to create a diagram in my project.
This didn't work (error "failed to register activex control" when dragging the tool into the form; although I registered everything successfully as an administrator) and many hours googling myself through forums made it clear to me, that this seems to be a general bug. At least I couldn't find a solution.
So now, I removed the tool MS Chart Control again, but still, I get error messages, when I build my project. After reinstalling Visual Basic 2008 Express Edition completely and removing all references that pointed on the MS Chart Library, I managed to delete some of them.
However three errors still remain, when I build the project. All of them of the same kind:
"Cannot write to the output file "C:...\Visual Studio 2008\Projects\Test\Test\obj\Debug\Test.Form1.resources".
Access to the path 'C:...\Visual Studio 2008\Projects\Test\Test\obj\Debug\Test.Form1.resources' is denied."
(same thing with two other files in the Debug-folder)
I again spent several hours searching through forums, but could not find a helpful answer. I already tried reinstalling everything again as well as rebooting windows and emptying the bin.
I also made sure, that the folder properties of 'Debug' are set on 'full access'.
Still, Visual Basic can not write on these files anymore.
I would be very grateful for any answer. Please note, that I am not an expert, neither on programming nor on computer-troubleshooting, so I would be happy about generally understandable (step-by-step) answers.
Many thanks in advance!
Regards,
c.
I just found out, that it works, if I open Visual Basic Studio as an administrator.
Strange, because a month ago, it always worked fine and I don't think I have changed anything about the folder or datas properties.
Anyway.... that solved the problem, I guess.
What's the reason for error message "The snapshot is out of date and cannot be used anymore because type tree has been updated, A new snapshow needs to be acquired"?
This error appeared right after I launched VS2010 and added username/pwd to connect to TFS repository.
I am using VS 2010 professional edition.
It happened to me with VS2012 as well after loading the project without source control binding, a local simple WinForms project. All I needed to do was Clean & Rebuild. After that the problem was solved.
This is a bug in Visual Studio. According to http://connect.microsoft.com/VisualStudio/feedback/details/742959/the-snapshot-is-out-of-date "We've taken a closer look at this problem and it isn't one that we'll be able to solve in the next release of Visual Studio."
They recommend waiting around until the background language parser service is done (or, in other words, don't try to be too productive there partner.) My experience is that closing all documents, cleaning the solution, rebuilding it and then closing and re-opening with a pause after does remove the error.
Until you do something silly, like edit code. Then all bets are off again as to when it reoccurs.
I had a similar issue with VS2012 and after rebuilding the solution twice, I still saw the same error message.
Following an advice from a post from this site, I closed the Designer tab, reopened it from the Solution Explorer, and the problem was resolved.
I got this error too, but after I unload project and reload project, the problem was resolved.
Simply restarting Visual Studio 2012 was a workaround for me, but it kept happening about every hour and having to restart visual studio that often was very annoying.
I also found this post which suggests that the Productivity Power Tools are the problem and to simply turn off the Automatic Brace Completion in Tools->Options->Productivity Power Tools. Since making this change I haven't seen the error message again :)
I'll note though that I am using Visual Studio 2012 and the OP is using Visual Studio 2010, but the Productivity Power Tools are available for VS 2010 too, so this may still fix the problem in VS 2010.
The same issue persists in VS2013, but no amount of Clean/Rebuild or restarting VS will help. The only way I can do a successful publish, is to disable the AutoT4MVC extension.
I got this error too. I closed Visual Studio 2012 and opened it again and the error was gone.
I got this error when I had conflicting class names / namespaces. I was referencing a UserControl from a different DLL in my XAML file which had the same name as my XAML file (class name). Maybe this helps.
I used Visual Studio 2012, and just faced this error on my Windows 8. It seems like Turning off the VM and restarting Visual Studio fixed the issue.
I just got this with VS2010.
I had a form with a user control (UCa) with a user control (UCa) from a different project on it. Made a change to the UCb then flicked to the designer for the form and boom! Snapshot error.
Resolved by a full clean and then rebuilding just the UCb project before building the rest of the project.
I'm using Visual Studio 2012, and I got this error when starting Visual Studio, letting TFS connect to the server, and THEN opening my solution. The fix was simply closing VS and launching the solution directly.
I'll throw my two cents in here as well.
I've tried every combination of Clean, Rebuild, Restart, etc. What I've found is that restarting Visual Studio usually makes the problem go away for at least one Publish. Here's the weird part, though. You can also fix the problem by doing absolutely nothing. If you just let Visual Studio sit for about a minute or two, and then publish, it will usually work just fine. There's some background voodoo going on here, and waiting for it to finish seems to do the trick.
I have a solution with two parts that need published. One is a WCF service application, and the other is the ASP.NET MVC5 website itself. Anytime I publish the services, and then try to publish the site I'll see this error. I can publish the services, restart VS, and then publish the site, OR I can publish the services, go get a drink, and then publish the site. As long as I give VS a chance to "settle" between any kind of rebuild and the publishing of the site, everything seems to work as expected.
Take a walk, come back, problem solved. OR if you don't have the time. Clean, Rebuild, Restart, Publish (lather, rinse, repeat).