I've installed Rider IDE on my Arch machine using flatpak, I face an error while creating new projects Unable to load project and obtain project information from MsBuild.
The error message says: Probably this project is incompatible with the current MsBuild.
MsBuild error details: Protocol connection was interrupted because the process has exited.
Anyone knows why it happens, and how can I fix the issue?
I have .NET6 installed and everything (including build process) works on VSCode.
I've tried cloning MsBuild from the GitHub repo and building it locally, but that doesn't help either.
After all, I tried all the solutions found on the internet and realized it was an issue with the Flatpak package.
I believe the maintainer forgot to put some required files in the package, or this might be a Permission related issue!
My suggestions to all the other user who might come to this once in the future are:
Learn Flatpak fully, so you be able to track what's not working and why!
If you're on an Arch machine, it might be a better idea to search in the AUR first.
Related
I just installed VS2015 community on my home machines. On my laptop, it works great. However I've run into an odd issue on my desktop. No matter what the reference is, it displays as unable to find (yellow warning symbol). It doesn't matter what or where it is. I have tried adding framework references (As basic as System) and references to external API DLLs in the local directory like Protobuf. NuGet will download packages referenced by projects I am working on and they will also be marked invalid. The properties for these references does not include a path, even when I specify one.
I'm a develop at work so I understand how to handle these issues generally. I've tried deleting the references and re-adding them, creating new solutions from scratch, pretty much everything I can think of and I'm out of ideas.
This is a Win7 machine with .NET 4.6.1 installed. I have tried changing my projects to target framework of 2,4,4.5,4.6, and 4.6.1 (no difference). This is a C# project if it matters.
Can anyone recommend next steps? Thank you.
I found the issue. Last month I tried to upgrade to Win10 and it didn't work out for me so I rolled it back. It deleted all the ACL information on all my directories. Specifically, the access to Microsoft.CSharp.Targets was lost. I restored that and everything worked again. Of course, now I have to try and fix every file and directory on my computer so I have access again. Thanks, Win10!
I came here just to find a solution to debug such kind of problem but no satisfying answer yet.
The original content as below:
The program I wrote in c# and WPF in VS 2013 is packaged by Installshield LE 2013, and there is no error during the package procedure. Then I ran the Setup.exe to install the program and there's nothing wrong either. However, after I run the program installed, nothing happened, neither error message reports nor visible windows, even I didn't find any process concerned in the task manager.
I can't figure out where the problem is, for there's no error or clue to analyze and investigate. Maybe something I missed when adding application files, I guess.
By the way, I used Sqlite as database and packaged the data file under the bin directory, is it one of the reasons?
I haven't used install shield but setup project can be an alternative solution to your problem.
Here is a link that explains step by step procedure of creating a setup project and .msi file afterwards. Have a look.
http://www.c-/UploadFile/dpatra/create-setup-and-deployment-of-wpf-application-step-by-step/
I've solved the problem.
It's not about InstallShield. It's about dependencies. There're two .dll files I didn't packaged, which resulted in the errors in running this program.
So I do the debugging by removing the files under Debug directory to judge which file is necessary to run this program. Maybe it's not a good way to solve such problem but for me, it worked after all.
I am writing a Visual Studio extension which targets VS2010, VS2012, and VS2013. It runs and is initialized successfully in each Experimental Instance with no issues. When I install the VSIX generated by the build, it installs in all versions without a problem, but only in VS2010 does it actually execute. In the others it's never instantiated or initialized.
There are no exceptions being thrown. Running the non-Experimental instance with the /log flag does not produce any other diagnostic information (other than confirming it is installed, and has a newer version than its counterpart already in the gallery.)
My reading and experiences suggest that this is due to some sort of missing assembly or reference, but I can't confirm that. I am also at a loss as how one would figure out what's missing, especially without an exception or log message.
I've been at this for several days now trying things like signing my assemblies, various vsixmanifest changes, changing the required framework versions, and many other things found here on SO that have not been fruitful.
Additionally, I have tried installing the old, already published version from the VS Gallery, and it also does not run. However, I have received feedback (bugs and thanks) from several individuals, so I know it works for some people. I have not received any feedback stating that "nothing happens," but do not rule out the fact that those are unreported.
I don't intend to plug, but the currently published version is here: http://visualstudiogallery.msdn.microsoft.com/5cc44f63-4ea8-4c17-8aa4-95037a2d32ef
The entire source for where I currently stand can be found on github in branch "ForStackOverflow". The difference between that and master is a TraceAppender which I used to confirm that the VSPackage was not being instantiated.
https://github.com/alexcpendleton/Pendletron.Vsix.LocateInTFS/tree/ForStackOverflow
Any suggestions, experiences, or anything would be helpful. Thank you.
Thanks to Erti-Chris Eelmaa's suggestion to enable FusionLog I was able to figure out what was going on.
Visual Studio was not looking for my extension in the installed extension's directory, rather from the GAC and elsewhere. Curiously, it was finding an included assembly just fine.
I examined the .vsixmanifest of other extensions and discovered that mine was missing a .pkgdef Content node for my project. It would seem VS2010 accounts for this, or for some other reason happened to look in the extension's installation directory for the package assembly, where 2012 and 2013 did not. Adding this content node to my .vsixmanifest allowed Visual Studio to load and run the extension.
<Content>
<VsPackage>Pendletron.Vsix.LocateInTFS.pkgdef</VsPackage>
</Content>
My solution can be built properly, with no errors on my workstation while the same source gives an error when building with TFS.
The solution projects target .NET 4.0 and I use VisualStudio 2012 on the workstation.
Using tfs.visualstudio.com (tfspreview.com) to keep the source, which I tried building with the Hosted Build Controller on tfspreview and with my own Build Controller that I host with TFS 2012 on my server.
I get the error in code where I use dynamic ExpandoObject.
Why my solution can't build on TFS?
I can provide more details if needed.
Have you tried the hosted build to see if that works?
Is is definitely the expandoobject? if you comment out that code does the build succeed?
can you send an excerpt from the build log?
I will post this as an answer as it solved this strange problem.
One of the project's solutions had two separate references to same open source library. One to the downloaded precompiled library, and one to another project where I kept the source of the same library. The first one was added by Nuget, the second manually.
The possibility to actually do this (add two references of same assembly) was probably a bug in Visual Studio or Nuget. Later when I tried to reconstruct this bug, an error message appeared, saying there is already reference to the specific assembly name.
For the compiling, I understand that TFS build agent considered only the precompiled assembly (Nuget package) and threw an error.
Visual Studio considered the assembly source which I modified to use with ExpandoObject.
Calling build command manually produced the same error as TFS did.
I removed both references and added only one (the other couldn't be added again anyway). That equalized the build behavior of TFS and VS for my solution.
I know this is very odd and I still can not remember how that double reference bug occurred in the first place. My guess is, this error can be reconstructed by editing the .proj file manually.
I have built a tiny wpf app that manages a website I am working on. The key feature of this app is that it allows me to checkout different branches of a theme repository. This works perfectly in visual studio, but when I publish, install and run the app on my windows 8 machine it comes back with:
{"Unable to load DLL 'git2': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}
I have searched through the internet and stackoverflow. There are similar questions, such as Unable to load DLL 'git2.dll' The specified module could not be found but the answers provided (as well as the answers shown in the github issue described in the answer) bring up another error:
Unable to find an entry point git_reference_oid in git2.dll
I have tried installing the latest through nuget, including a compiled dll and adding the git2.dll, including the libgit2sharp project in my solution. Once again, it works perfectly when I run it all through visual studio, but fails when I publish, install and run it.
I was unsure what information needed to be included so please feel free to comment and let me know so I can update the question.
Thank you!
The computer you're running the installed executable on may lack MSVCR100.DLL or MSVCR110.DLL (depending if git2.dll has been compiled using Visual Studio 2010 or 2012).
A fix has been recently merged in libgit2 which removes the need for this dependency.
Indeed, running dumpbin /IMPORTS git2.dll against those binaries doesn't show any dependency against MSVCR1x0.dll any longer.
The latest tip of the vNext branch of the LibGit2Sharp project embeds those updated git2.dlls. It's recommended to compile the project (using the build.libgit2sharp.cmd tool and use this version (manged assembly + native binaries) instead).