VS2015 F# compilation error Microsoft.Common.CurrentVersion.targets - visual-studio

Please help !!!!
I don't know how it exactly happened, but my VS2015 looks f*cked up and I can't compile my projects anymore...
I just remember excluding by mistake a .fsx file from the project in solution explorer and tried to reinsert it again
but maybe this isn't the cause, and its due to some automatic update ?
when i compile my program i get this error
I tried creating a new project, reinstalling Nuget packages in the new project, copied/pasted the old source .fs files into new files in the new project, but i still get the error
i don't think it has anything to do with Seq.tail, anything other program will have something underlined as well, but the Microsoft.Common.CurrentVersion.targets warnings remain
I'm thinking about reinstalling everything but will it solve the problem ???
I feel really desperate... Thanks very much to anyone who can help

Related

Missing maui_colors.xml and maui_splash_image.xml

I've been developing a .NET MAUI app on my Windows 11 machine which works perfectly.
When I try to compile and run it on a Mac, running the latest version of Visual Studio for Mac - 17.3 Preview build 1038, I get two errors -- see below:
Source file 'obj/Debug/net6.0-android/resizetizer/sp/maui_splash_image.xml' could not be found (XA2001)
Source file 'obj/Debug/net6.0-android/resizetizer/sp/maui_colors.xml' could not be found (XA2001)
Any idea what's causing this and how to fix it?
P.S. I started this project from scratch on my PC so it's not a conversion from Xamarin.
Cleaning and building the Solution (not the single project) fixed it for me.
UPDATE: Rebuild also works. Sometimes you'll have to do this twice it to work.
Cleaning, and then building the solution then resulted in error code = "AMM000" on File "AndroidManifest.xml". I found virtually nothing on that code.
Ultimately, I spent a few hours creating a new project and moved my code over to the new project, line-by-line.
Not a great bug. I believe all that I did was change my icon file, but I guess I'll rename my actual icon to the sample "bot" icon that comes in the sample project and leave it at that.
I had this problem when creating the APK for my MAUI app. Cleaning and rebuilding as the other answers suggested did not work.
I solved it by creating a new MAUI project and going through the deployment process to generate the files; and then replace my actual project files (my problem was in the resizetizer folder) with the generated ones. This got rid of the error.

Issue with CMake setup in Visual studio

love to get some help regarding an issue with the Cmake extension in VScode that im hoping someone has experienced before, I'm driving myself mad on this small error. I am completely new with VScode so please let me know if you need more infomation, anyway the error when i try to build is;
Bad CMake executable “”. Is it installed or settings contain the correct path (cmake.cmakePath)?
I am using windows and have tried adding the Cmake location to my path, even tried on another laptop but nothing is working. Any help would be amazing.
Cheers.

Importing a project into Visual Studio. Why so many errors?

This isn't really coding specific, but we currently have a project that is live and working fine. I am tasked with making a few changes to it. I imported the ALL files of the project to Visual Studio 2010. I can't get any work done, because of all the errors!
Do you have any suggestions for me? The project doesn't have a source file, so I created a project and made one myself.
I tried another version of Visual Studio, and the errors continue. How in the world is this project even working?
Also, I have no way to speak with the creator.
Thanks for the help!
Josh
Without seeing the specific errors you're running into, I'm guessing that you are hitting one of two scenarios:
The source code references .NET assemblies that you do not have installed on your development machine. The only way to correct this is to get your hands on a copy of those assemblies to install them. The assembly names should be in the error messages, which would give you a good starting point to look from.
It's also possible that differences in the .NET framework versions that it was originally developed in and what you are trying to use now are accounting for a large number of errors. If the errors specifically reference the version number, this is most likely what you're experiencing. If this is the case, there are ways you can upgrade the individual file versions that your program references, but I honestly haven't done that in about 8 years, so I'm drawing a blank at the moment as to how to do it.
I don't understand ?
you have a "project" (what kind of project?) that you want to start working with with VS2010 ?
You add the files to a new VS2010 project and start building it and many errors occur ?
What kind of errors ? Language (C++/C#) errors ? missing include missing ? missing libraries ?
Can you show a some of the errors you get ?

OBJECTIVEFLICKR: systemconfiguration.h not found

I'm implementing ObjectiveFlickr into my project and I'm very VERY new to all of this (C language and Xcode included).
I managed to fix a few compile errors and I'm down to this one that just popped up after I added some supporting files to get rid of the other errors:
systemconfiguration/systemconfiguration.h file not found
I have no idea what this means and have done much searching online before posting here, but the only resolution to another poster's issue was to re-install Xcode. I'm sort of doubting that will solve this problem as I've had no issue with Xcode up until this error.
Can anyone spare a tip or two in layman's terms to help me get past this? I've been searching for 24 hours and the only link to the Apple Developer forums isn't working, go figure.
Any help is appreciated. Thanks in advance.
XCode can be very picky about where to look at in terms of header files.
If you got yourself a .framework folder, then click in your project, choose "Build Settings", then look for one called "Header Search Paths". Put the framework's path in there, and change the box on the right from "non-recursive" to "recursive". This should get the build going, and works for almost all third-party libraries.
If, on the other hand, you're trying to compile the library with your app, double-check to see if you didn't forgot to include some file in your XCode project, or if it is not marked for compilation in the project settings (.h files do not count, but maybe the source of your problem are some extra .c or .m that shouldn't be there).
If all else fails, since XCode projects compile into a "flat" directory tree, you could try removing the folder indicator from the #include: from "systemconfiguration/systemconfiguration.h" to "systemconfiguration.h", from the files where the .h is called. This worked in some cases of mine.
There is a framework in iOS called "Systemconfiguration.framework". Add it may help a lot.
Hope this may help you.
I had blanks for some reason in my code around the header decaration
#import < SystemConfiguration/SystemConfiguration.h >
I removed them and it worked.

Xcode reports errors, after building successfully

Xcode 4.5 (but also earlier I think) reports build errors, but I just created a successful build. And it also depends on which file I select in the project browser. Some files give errors, others don't.
This leads me to believe that there is a bug in the auto evaluation of my code. It seems to loose the #imports or deeper links to other headers...
I have been without the problem for a while, but today it returned. Very strange and annoying.
Is there an autocompletion cache to delete or something.
(Deleting derived data didn't help, or cleaning the build.)
Has anyone found a way to fix this?
edit: still happens in Xcode 4.6
Might help to use #class more in headers, but unverified.

Resources