I'm working on a project, and it uses a few libraries (RestSharp, Newtonsoft.Json, CsQuery) and I didn't want to use the exe with all the dlls in the same directory, so I also installed Costura.Fody, and that worked when I used Visual Studio, but now I'm using JetBrains Rider EAP, and the output exe file does not include the embedded dlls/ If I move it, It crashes saying something like "Cant load CsQuery" etc.
I'm running a 64 bit version of Windows 10, Visual Studio 2015 Community Update 3, and Rider EAP 15.
Anyone else having thing problem/know how to fix it?
Looks like a bug which makes Costura.Fody useless while using Rider EAP. After switching to Visual Studio 2015 Community and re-installing Costura.Fody in project and compiling - everything works fine and dll's are embedded.
Compiling with Rider EAP doesn't embed any dll's.
Related
I am trying to switch from Visual Studio to Rider. For that, I need Rider to be able to import a third-party SDK (ArcGIS Pro SKD from Esri). This is available in the Visual Studio Marketplace but not in Rider. I also have a vsix installer package for offline installation. There is no ArcGIS plugins in the Rider marketplace, and if installing it looks like Rider wants it in some packaged form. The SDK installation contains all sorts of librarys and templates. If i can't install them, it basically renders Rider a useless tool for me.
What are my options here? I am basically assuming that a VS plugin should work in Rider. Is this Assumption flawed?
Esri only supports VS 2017 and 2019.
https://github.com/Esri/arcgis-pro-sdk/wiki#requirements
You cannot use a .vsix installer with rider so you are out of luck with regard to official channels. You could try creating your own build target in Rider following this guide.
You want your Rider build target to point to
"C:\Program Files (x86)\MSBuild\Esri\ESRI.ArcGIS.AddIns.11.targets"
or whatever the equivalent is for the version of the Esri SDK you are using.
Good luck.
My computer has Visual Studio 2013 installed.
I tried to compile some source code but it doesn't work.
It is C# language and it uses namespace Microsoft.TeamFoundation.VersionControl.Client
When I install VS2010, it compiles well!
I find that the source code use VS2010 Microsoft.TeamFoundation.VersionControl.Client's dll file.
How can I solve this problem?
Your application are trying to referencing dlls Microsoft.TeamFoundation.VersionControl.Client from the GAC.
One solution is just as you done, install VS 2010 on the development environment and referencing the Microsoft.TeamFoundation dlls from the GAC. VS 2010 installed version 10 of the Team Foundation dlls into the development GAC.
However, this will cause you need to also install VS2010 on the build agent. A better solution is using Nuget Package. These have been moved into a Nuget package.
They're also stored under the "CommonExtensions" folder of your Visual
Studio installation, but these are not meant to be referenced anymore,
that's what the NuGet package is for.
C:\Program Files (x86)\Microsoft Visual Studio 1x.0\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
Take a look at this similar question: Where can I find Microsoft.TeamFoundation.VersionControl.Client.dll in Visual Studio 2015 installation?
I have Visual Studio 2013 Ultimate. Today when I opened it, it didn't load any of my solution's projects. Error message:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- ETL_<Project name>, "<Project path></Project>.csproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- <Project name></Project>, "<Project path></Project>.sln"
These projects are of types Class Library and Console Application. If I try to create a new project, these types are listed, but when I create it I get message <Project path> cannot be opened because its project type (.csproj is not supported by this version of the application. To open it, please use a version that supports this type of project..
So, Visual Studio is telling me it doesn't support a project it just created?! GJ M$!!
Unfortunately I was unable to solve this. I ended up uninstalling VS Ultimate. Now I use VS Express for Desktop, and it works with my old projects.
My assumption is that something on Windows broke some part of VS. I should have tried to uninstall and reinstall it but didn't have the opportunity.
I have the same thing in a Hyper-V VM. After repair did not work, I deinstalled and reinstalled VS 2017. Same thing.
In the host I can still open the same project with VS, so it is not the project, but the VS install that has a problem.
It puts this in the migration log:
src\DTOWEB\project.json: Failed to migrate XProj project DTOWEB. Could not find project.json at C:\DTOWeb\DTOWEB7\src\DTOWEB\project.json.
I have a second VM that is x86 iso x64, and it can open the project without problems. So again, my conclusion is there is nothing wrong with the project.
I have had a project in VS 2015 Update 3 with a lot of code logic behind. I upgraded it to VS 2017 RC successfully. The code implementation went on and on until getting to the point where VS 2017 RC exhibited a lot of issues and instabilities e.g. .Net Core DLL template removed! by installer or Resource file could not be compiled and so forth! I'd like to revert the solution back to VS 2015 to keep working flawlessly but it's impossible easily due to a lot of code implemented in VS 2017 excluding new Roslyn features. Any suggestions how to perform the downgrade?
You will also need to update your *.vcxproj files, to change the toolset referenced there to the one used by the earlier compiler.
What I found useful, is to create a small scratch project (just simple console app) in each version of visual studio, then use beyond compare or similar to contrast the .sln and .vcxproj files from each vs version. This will show you the toolset changes and maybe a few others that you need. For example going from vs 2017 to vs 2019 the toolset changes from 141 to 142.
So the lines
<PlatformToolset>v141</PlatformToolset> are for vs2017
and
<PlatformToolset>v142</PlatformToolset> is for vs2019
It's indeed a manual process and no there are no tools that can automate that.
I had the same problem and i fixed it using this solution:
1) create a solution of whichever project you want (winforms, etc)
2) browse to your project folder and find your .sln file.
3) open it using notepad.
4) copy the first 4 lines as shown
here.
5) find your .sln file for the project you wish to downgrade. for example : foo.sln (its found where your project is).
6) open it with notepad and paste the lines instead of the first 4 lines
7) save and open the sln. it should open it under visual studio 2015
i hope this works for you
I want to build a C# app that uses the Roslyn NuGet packages. I have Visual Studio 2013. Things were going fine until I hit a ReflectionTypeLoadException looking for Microsoft.Build version 14, which I take it comes with VS 2015 CTP (see this question).
My question is, how far can you get with Roslyn without running into this issue? Do you just need to avoid using the MSBuildWorkspace class? What are the alternatives? Is it possible to download and use the Microsoft.Build assembly from 2015 while still using the 2013 IDE?
You need to download the MSBuild 14 tools from http://go.microsoft.com/?linkid=9863815