I'm working on a WP7 project and noticed that VS constantly checks out WMAppManifest.xml. As far as I can tell this happens regardless of what type of code change I make. Is it possible to prevent this behavior or is it necessary?
Same thing here, the file is checked out every time I build a project and it is not modified. The file is always the same as before. I am using TFS. Looks like a bug.
This appears to be fixed with the latest Mango tools released with the 7712 build.
Related
I recently upgraded Xamarin Studio to the latest version, and now I am unable to load my solution!
Upon opening the solution, the below error is displayed:
I have looked into the logs, and I see the following:
System.InvalidOperationException: Already bound to project
Has anyone seen a similar error, or does anyone have a solution?
Thanks!
This error appear to be associated with the following Xamarin bug report:
https://bugzilla.xamarin.com/show_bug.cgi?id=41565
If you are able to try the following workaround, it should allow you to open the project.
Back up the solution
Open each .csproj file associated with an extension (such as WatchKit or Today)
Find the section "ProjectTypeGuids"
Remove the key "FEACFBD2-3405-455C-9665-78FE426C6842"
Save the file
Attempt to open solution
This should solve it for iOS
This also appears to impact Android projects which contain bindings. For example:
Given a test project (Test.csproj) with two ProjectTypesGUID: {EFBA0AD7-5A72-4C68-AF49-83D382785DCF} and {10368E6C-D01B-4462-8E8B-01FC667A7035} the project will fail to load. This is because the first ID corresponds to a regular Android project. The second one is for an Android Binding library project. The problem can be solved by removing the {EFBA0AD7-5A72-4C68-AF49-83D382785DCF} GUID from the .csproj
Fixing the issue for Android is similar to above. If the project contains both ProjectTypesGUID: {EFBA0AD7-5A72-4C68-AF49-83D382785DCF} and {10368E6C-D01B-4462-8E8B-01FC667A7035} then do the steps below
Back the solution up
Open the .csproj file
Find the section "ProjectTypeGuids"
Remove the key "EFBA0AD7-5A72-4C68-AF49-83D382785DCF"
Save the file
Attempt to open solution
Thanks!
Hope it helps :)
My xamarin project was made at windows, I copy to Mac. But Couldn't open same error. I solute with doing this. Open solution from windows visual studio. and right click solution then open xxmanager(i don't know english menu name, short cut maybe "o") and check build IOS. and copy to all solutions and project files to MAC. Then retry open solution. good luck
I have been experiencing this issue for hours. It started suddenly when Xamarin.iOS was giving issues due to lack of reference.
I tried the solutions here including removing the guid in Project Build but nothing worked.
To fix this, I realized that Visual Studio for Mac had downloaded an update which I installed and restarted immediately. I then noticed that Visual Studio Xamarin Form iOS component is missing at it states the presence of an update to 12.xxx.
I simply re-downloaded the iOS components (about 550Mb) and I am hoping everything would work fine.
I’m having a problem when debugging my Android app. When I start debugging, then stop, then start debugging again, it will always re-install the app on the phone even though there hasn’t been any changes done. This can start being a pain since our app is large and each build takes over a minute to complete. As far as I can tell, I’ve set everything correctly, including having Fast Deployment turned on and having the linker disabled to speed up the build process but it still rebuilds, uninstalls and reinstalls the app, taking up a lot of time. One thing to note is that we don't see this behavior in Xamarin Studio on the mac, it’s only within Visual Studio.
I’m running visual studio 2015 14.0.25123 update2 with
Xamarin Android 6.0.3.5 (a94a03b).
Please help me resolve this issue.
Thank you.
Based on the information you've provided, it seems like you're hitting a recent issue we've seen with NuGet packages and dating. The new NuGet client for Visual Studio will now honour the dates found inside of the .nupkg, instead of using the current date when writing files to disk.
What this means is that packages with odd dates in their files, like the popular ModernHttpClient library (which dates its files using 2046) will end up written in disk with those dates. As a result of this, msbuild will detect this future date upon build and assume your app is not up to date and will then fire a complete rebuild, essentially breaking incremental build support.
You can check that this is the case by turning on msbuild diagnostic output. The very first line in the build output pad should read something like:
1>Project 'App3' is not up to date. Input file 'c:\temp\app3\packages\modernhttpclient.2.4.2\lib\monoandroid\okhttp.dll' is modified after output file 'C:\temp\App3\App3\bin\Debug\App3.pdb'.
To fix it, you can touch the date of the offending .dll to the current date or download the NuGet packlage from the NuGet website, then extract using Windows built-in .zip support (you must use the Windows built-in support other utilities may keep the bogus dates).
The following VS extension was also created to automatically touch the dates of offending packages and is definitely the easiest way to get things sorted:
https://visualstudiogallery.msdn.microsoft.com/0ffd5d55-6d03-4be1-95b5-a94c89af86ba
Do note that this issue does not manifest if you're using Xamarin Studio.
I recently installed Dotfuscator 4.10 on my computer and I already has VS 2012 working on it. Everything worked fine up to the point when I tried Dotfuscator embedded in VS (I mean the standalone GUI app works perfectly).
Just for the try, I created a small solution (no TFS/VSS) with a C++ /clr app, a C++/clr dll and a C# app.
I then added a Dotfuscator project. To this project I added the output from the three dll/exe other projects.
When I tried to rebuild the solution, I was asked to save the .dotfuproj file. Strange and abnormal behaviour, the file should be saved automatically and without prompting me. OK, I chose to overwrite the existing file (what should have been done automatically after all.) I got the error Object reference not set to an instance of an object. I had to cancel the operation and could not build the solution.
Note that I observed the same behaviour if I tried to save the dotfuproj file under an other name. Also, the file is not R/O.
My question: has someone experienced this problem? Any solution? Thanks for your help!
You can try deleting your Dotfuscator project and then creating a new project. If that does not work, try using direct input to the Dotfuscator project, rather than using the output of another project within your solution.
I have a Visual Studio 2010 Ultimate C++ project (not managed or .NET). When I press F5 (i.e., start debugging), I want it to save all the files, rebuild those that changed, link the whole thing, and then run. Instead, it appears to use the last build. Thus, when I try to step into a function or something, I get the following error:
Based on my research, I have verified these options, the first three of which are in the Options dialog (can be reached under "Debug->Options and Settings"):
"Projects and Solutions->Build and Run->Only build startup projects and dependencies on Run" is checked. Some research indicated that it should be unchecked, but in my case I actually do only want it to rebuild the startup project. For what it's worth, I've tried unchecking it, with no effect.
"Projects and Solutions->Build and Run->On Run, when projects are out of date:" is set to "Always build".
"Debugging->Edit and Continue->Enable Edit and Continue" is checked, though it's greyed out.
In the Configuration Manager ("Build->Configuration Manager"), all solution configurations and platforms have their "Build" checkbox checked.
I have also tried deleting all Debug and Release directories as well as the .sdf and ipch directory.
For completeness, I suppose I should mention that I'm using precompiled headers, though I kinda doubt it matters.
[EDIT: I should note that it only seems to be one file (a .h file) that's doing it. I tried renaming it and recompiling, and also removing it from the solution and adding it back in, but it didn't work. ]
I was able to bring my solution back into the right state after deleting all .suo and .csproj.user files. Answer led to this solution. Hope this saves someone time.
I fell into this state after installing Ultimate over Professional and running profiling tools.
Once I had similar problem with my C# project and I think I have tried every possible suggestion available on internet but none worked and then this is what I have done:
Created an empty Project
Added startup function to verify that it does not show any error
Imported all my source code manually one by one
So, Yes, it was the solution. You already have done a lot so I would say you can get lucky by trying here and there however having a new project and importing your individual source file would be faster.
Another solution could be that switching the platform. I noticed that when I when to project properties, the new project I had just created had a platform of 'win32' and my other projects in the same solution had it set at x64. After I switched my project to x64, everything worked just fine. This worked for my interop(C,C+, C#) project and hopefully works for other projects as well.
I have successfully resolved it, try the following:
remove all temporary and intellisense files
remove all project from solution and then add them back(most important)
check projects 'Frameworks and References' to ensure they are valid
From a few days ago I'm facing annoying problems with Visual Studio and .net framework.
First I couldn't use breakpoints, but after a few changes I'm able to.
Yesterday, I've changed my Model of Entity Framework and renamed a few columns. Now the web server assumes that no change have been made.
I've made a simple test: removed a condition that I had in my masterpage where I checked a session and created a breakpoint there, when I run it VS goes to the breakpoint, the condition isn't there but he keeps working like it was.
I've tried to use the fusion log to check assembly errors on run time but none give me errors.
I can only assume that I'm not running the "newest" version of the project but I don't know why.
It sounds like your dlls are out of date. Try using the option "Clean Solution" and then re-build the solution.