I'm opening the CodeRush shared sources, e.g. CR_CommentPainter in Visual Studio 2008 and 2010, but Visual Studio is complaining about missing file. AssemblyVersionInfo.cs
Anyone shed any light ?
The shared source plugins share a common AssemblyVersionInfo.cs file..
The file itself is held in the shipping solution folder. This is the common 'Source' folder in which all of the shared source projects sit.
Therefore if you're trying to locate the AssemblyVersionInfo.cs file for CR_CommentPainter and the project itself is stored in CodeRush\SOURCES\CR_CommentPainter then the AssemblyVersionInfo.cs file should be in CodeRush\SOURCES
It is entirely possible that you may have chosen to copy the CR_CommentPainter folder elsewhere for experimentation purposes.
If this is the case then you will not have copied the AssemblyVersionInfo.cs file from it's parent folder and as such, visual studio will be unable to find it.
If for any reason this file goes missing, the latest (11.1) version of this code is
using System.Reflection;
using DevExpress.DXCore.LicenseUtils;
[assembly: AssemblyCompany("Developer Express, Inc")]
[assembly: AssemblyProduct("IDE Tools for Visual Studio .NET")]
[assembly: AssemblyCopyright("Copyright (c) 2003-2011, Developer Express, Inc")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyVersion(DevExpress.DXCore.LicenseUtils.AssemblyInfo.Version)]
[assembly: AssemblyFileVersion(DevExpress.DXCore.LicenseUtils.AssemblyInfo.FileVersion)]
.. and it appears currently to only vary from previous versions, by copyright date.
Related
Using VSTS (not git) and use Visual Studio 2017 libman to manage client-side libraries. These libraries are put in wwwroot\lib. I don't want to add these to source code control.
I've tried putting a .tfignore in my project folder with:
wwwroot\lib
I also tried:
\wwwroot\lib
Regardless of what I do, all the wwwroot\lib files are put in source code control when I add a new client-side library via libman.
How can I ignore the lib files since they are managed/restored by Visual Studio libman feature?
Based on the comment above from Seabizkit, **/wwwroot/lib worked for me.
We are planning to switch to Visual Studio 2017.
For our Entity Framework 6 edmx file we use the EntityObject Generator extension to create us the desired ObjectContext.
This extension is only compatible up to VS2013 - inofficially up to VS2015. The solution to simply adjust the manifest file in the vsix does not seem to work for VS2017 though - I guess among others because the vsix architecture changed.
Is there a way to get the ObjectContext template without using an old Visual Studio? I assume the template is not always the same for each edmx file so it could simply be copy pasted from an existing project.
I just did this in VS2017.
Download the VS extension package "EF 6.x EntityObject Generator for C#" from MS. It's a *.VSIX file. Rename it to ZIP. open the zip file and inside that you find one more zip.
There you will see a TT file. Copy it out.
In your project that have a MyModel.TT file that generates DbSet just replace that TT file with the one you got from vsix file.
Edit one line:
SourceCsdlPath = #"$edmxInputFile$",
to your
SourceCsdlPath = #"myEDM.emdx",
save TT file and your c# model code is generated with old EntityObjects
.cs project file
The project was created using Visual Studio 2010 and I am trying to open it in Visual Studio 2010 itself but still I am facing this problem.
I have opened this project in VS 2012 and worked for few days but it has created in Visual studio 2010. Is there anything which preserve the project details on local machine?
This is the specific project section in my solution file:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Project Name", "Project Name\project name.csproj", "{48C1190E-7700-461B-ADCD-B5E0F1ECAD21}"
ProjectSection(ProjectDependencies) = postProject
{1F5440B3-9FD8-4FE2-B621-8697489ABDC4} = {1F5440B3-9FD8-4FE2-B621-8697489ABDC4}
EndProjectSection
EndProject
In Visual Studio it is possible to add Project Types, e.g. for creating an MSI, by installing an Add-On to the development machine. It appears that in the past this was done, and then that new Project Type was used to add a Project to the Solution. But now you are opening the Solution on a machine that does not have that new Project Type.
Look for the GUID of the missing Project Type, it should be part of the error you are getting. Then google "project type {the-guid}" to see which Add-On you need to install on your development machine.
It is also possible that a new Project Type was used in the Solution that simply can not work with VS 2010. In that case your options are either to keep using VS2012, or to start over with a new Solution in VS2010 and migrate the projects into it that are compatible (which may be a bit tricky or hard to do if VS2012 saved them).
Would it be too difficult to just recreate the project and include all the necessary files and references? Once the project was saved from VS 2012, the format may have broken compatibility with 2010. Sometimes this is fixable just by updating the version number in the project file, but I don't see it in your image.
I want to create a simple application with a few static libraries from OpenCV. I managed to link all necessary .lib files, including opencv_world300d.lib, but at run-time it requires the opencv_world300d.dll. I can add the directory where this DLL is, but I just want a single .exe (no additional files). I clicked everywhere the option \MT or \MTd (no dlls)
How can I achieve this?
It is for x86, visual studio 2012 (v110) and OpenCV, version 3.0.0. In the lib file there is a reference to the dll, unfortunately.
OpenCV application on MS visual studio c++ needs a DLL?
Not necessarily. You can link to OpenCV static libraries, which are in the folder staticlib, under OPENCV_DIR/build/.../staticlib.
The libraries in the lib folder are for dynamic linking, so you need also the .dll.
You can have a look at this answer for the step-by-step configuration.
I am using WSPBuilder on Visual Studio 2010 to create a feature with a feature receiver assembly for SharePoint 2010. When I try to build the WSP using WSP Builder I get this message in the output window:
The assembly MyAssembly.dll is unmanaged. The assembly will be excluded from the WSP package!
The defined Project Assembly seems not to be a valid assembly!
Solution compatibility: SharePoint 2010
The resulting WSP that gets built does not contain my DLL.
My DLL is strongly named, and I cant think of any other obvious reasons why this is happening.
Any idea why WSPBuilder is not able to package my assembly in the WSP?
Ahh... Found the answer. My code was getting compiled against .Net Framework 4.0. Changed it to .Net Framework 3.5 and Voila! WSP gets built without any problems...