I'm moving my old project to Visual Studio 2017 [from 2015], but whenever I try to edit a RDLC report in VS it updates my report version and makes it incompatible with 'Microsoft.ReportViewer.WinForms' version 10.0 using 12.0.
The thing here is that I need to keep the version, because every user has the v10.0 DLL aside the project so I could not update everyone at once.
I tried to embedded that DLL into the executable but it says this:
Cannot embed interop types from assembly
'Microsoft.ReportViewer.WinForms, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91' because it is missing the 'Guid'
attribute
Any help or workaround would be appreciated, thanks in advice.
For anyone wondering how to do this, I didn't found a workaround.
Instead I decided to upgrade to latest ReportViewer version [10.0 -> 14.0] as it has retrocompatibility, it can read older reports and I don't have to upgrade them.
In other hand for the fact that I have several user installations with the DLL in the same folder of the executable, I have an automatic tool which allows me to update any assembly without much effort. This tool is made by me, so I can't tell how to do it other way.
Related
I have a C code (pretty old one) that I tried to run in VS17 and am getting this error:
The build tools for Intel C++ Compiler 17.0 (Platform Toolset = 'Intel C++ Compiler 17.0') cannot be found. To build using the Intel C++ Compiler 17.0 build tools, please install Intel C++ Compiler 17.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
I am not including the code as it is old and big.
Can someone please suggest what the problem is?
It means your project configuration was done with an old version of Visual Studio.
I suggest you follow the VS suggestion: at the solution pane, right click on the project/solution and select 'retarget solution'. This will change your solution/project configuration to the current visual studio you use (2017).
As the project/solution files will be overwritten by the 'retarget' process, it worth copying the solution/project files (or even the entire solution
directory) before starting the 'retarget solution' process, so you can revert to the previous state for troubleshooting etc.
An example:
I'm want to build an old version of librdkafka, which was originally built with VS2010, and I want to use VS2017.
when looking at the solution explorer pane, you can see all projects has "(Visual Studio 2010)" title near them, at the left side of each project name.
Now I right click on the solution, and select 'Retarget solution':
At the dialog box, you get, click OK, and that's it.
I've moved a C# project from Visual Studios 2008 Professional to Visual Studios 2010 Express.
It converted the project successfully with the VS migration wizard, but the build is failing.
There are quite a few errors, all having to do with the WPF Datagrid. The errors don't occur when built in VS2008. For example:
'DataGridRow' is an ambiguous reference between 'System.Windows.Controls.DataGridRow' and 'Microsoft.Windows.Controls.DataGridRow'
I see that the project also uses WPFTools.dll.
With VS2010 maybe WPFTools.dll is no longer needed? Or maybe I need to use the Professional version instead of the Express version of VS and the project wasn't successfully migrated?
I think I can edit all the places where this is a problem using the full namespace to make the error go away, specifying either "Microsoft.Windows.Controls" or "System.Windows.Controls", but I'm not sure which of the two it was defaulting to under VS2008.
This is most likely tied to the .NET FW version, ie...was this 3.5 prior and you migrated to 4? If so, you would have been using the WPFToolkit prior whereas the DataGrid is now part of the standard FW in 4 and greater.
Remove your references to the WPFToolkit and use the standard FW class and you should be fine.
Error. The type or namespace name 'GridViewExpressionColumn' could not be found (are you missing a using directive or an assembly reference?)
Hello all,
I've inherited a VisualStudio 2010, Silverlight 4 project with a custom RadControl from Telerik. The project runs fine on the server, but I would like to make some changes locally. When I copied the project folder over to my c drive, the application cannot compile (build errors). After cleaning the solution, I still keep running into CLS-compliant issues, and most notably, the error listed above. I'm not sure what the problem is, since I've never worked with Telerik or third party RadControls. Any help would be appriciated.
Thank you.
You will need to contact your office software guru and get a licensed copy of Telerik RadControls to install on your local development machine.
To get you compiling, for now, you can use the demo version available at http://www.telerik.com/support/demos/developer-tools-demos.aspx - any solutions compiled from this will show a big "DEMO" banner accross the control for a few seconds.
I built a WPF application in VS.NET 2008 using ClickOnce deployment. It ran great on any machine that had VS.NET installed, but my business users received an error: "Unable to install or run the application. The application requires that assembly Microsoft.Windows.Design.Extensibility Version 3.5.0.0 be installed in the Global Assembly Cache (GAC) first."
I was surprised to discover that this dll is not part of the standard .NET 3.5 SP1 client installation, but somehow, my application thought it was needed. I checked my Publish tab for the project and it showed up as a prerequisite.
Oddly enough, I was able to just remove this (and all of the other Microsoft.Windows.Design.* dlls) and it just worked everywhere. I removed them from my project entirely, and everything was fine.
Can someone explain why the VS.NET 2008 project wizard forced these to be included in the project, and more importantly, why ClickOnce thought they needed to be on the client machine to run?
This is just a curiosity question, but I'm sure I'm not the first to be bitten by it. Hopefully, this post will at least save someone else the headache.
Try to remove all references to *.Design.dll. In my case it was WPFToolkit.Design.dll.
This is old and the OP is gone, but I ran into this today, so I thought I'd mention that my solution was removing a reference to one of the WPFToolkit references that ends with .Design.
I had referenced System.Windows.Controls.Input.Toolkit, but also had a reference to System.Windows.Controls.Input.Toolkit.Design, which should not have been there. Removed it, and all was right with the world again.
A way to find out the code that is loading the assembly is explained here:
http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/755272f6-0e79-4a6d-ae50-4412d0f2bc4c
I found that I was using the SelectionCommands.Clear property which is inside the Microsoft.Windows.Design.Interaction namespace inside the Microsoft.Windows.Design.Extensibility Version dll.
Beats be why this dll isn't included in the .NET 3.5 install.
We are using Visual Studio 2008 to develop a winforms application stored in Visual Source Safe 2005.
If one of our team members changes a *.Designer.cs file without changing the form's source file the change doesn't appear during a "Get" operation. However, if in Visual Studio you run a compare on the *.Designer.cs file the differences are displayed in the difference viewer.
FYI: We are using the default Microsoft Visual SourceSafe plug in for Visual Studio.
Any ideas why the "Get" operation will not detect changes in the *.Designer.cs files and suggest we pull down the latest version?
Thanks for your help!
Designer files are not intended for manual manipulation. One of the chief incentives for adding partial classes to the popular .Net languages was to segregate the designer-generated code from manual user code, in fact. Manual manipulation of repeatedly-generated code (in pretty much any environment, not just visual studio) is asking for headaches.
What changes are you making to the designer file, and why is it not possible to make those changes to the non-designer source file?
Edit:
Is the project in the IDE properly bound and connected to the source control database (via File->Source Control->Change Source Control)? It should automatically be checking out the designer files when changes are made in the designer view.
I would try doing a Get manually through VSS Explorer (i.e. not through Visual Studio) and see if it works. If not, check to see if the file is pinned to a previous version.
Woe unto you for having to use SourceSafe. At my last job, we used SourceSafe and had a myriad of problems with it. We switched over to Surround SCM and were really happy with it. I'd never heard of it before that job.
To answer your question, any time I ran into a problem like this with SS, I'd do a "forced get": in the options dialog when you get latest, tell SourceSafe to get the latest version from the server regardless of whether it thinks the file is up to date.
Edit: I think the issue is the VS200X plugin for VSS. If you have the VSS standalone application you should be able to do a forced get from there. I now remember having to do this so often that I stopped using the VS200X plugin.