I have a problem about using added references on VS2012.
I added System.Runtime.Caching in my projects references, but I can not call it from classes not event its namespace.
I've already tried closing and restarting computer. My .Net framework version is 4.5, not ClientProfile.
Did anybody get this problem before and is there a solution for it?
Related
So I started with VS2017, SQL 2017.
Created a script task which by default is .Net 4.5, and installed RestSharp.
Error.RestSharp needs 4.5.2, so I changed my framework in VSTA and hey-presto, everything installed, built and saved.
Now, close VSTA, close the script task, then reopen both - only to find that the project has reset to .Net 4.5. References to RestSharp are now invalid.
After some googling, someone said that when using SQL2017 the framework in SSIS gets fixed to 4.5.
So, I changed to SQL2019, now only to find that the framework gets fixed to 4.6 - which causes the same errors as previous.
By behaviour, it looks like RestSharp only works with very specific versions on framework, and that is not configurable in VS !!?
Anyone have any ideas ??
Thanks
I'm creating script tasks in SSIS packages using the free BIMLExpress. Since we have different versions of .NET Framework installed in our environment I really need to be able to set the Framework version for the script project. Although I know how to change it manually, it would be very difficult to change it manually.
I have already tried looking for a solution and this answer suggests to use TargetFrameworkVersion property but I don't see that property at all, I've tried using it with no effect. I don't know if it only works with BimlStudio the paid version.
I'm using BIMLExpress 5.0.61915.0 with Visual Studio 2015.
Any help is greatly appreciated.
Thanks
I opened the generated .dtsx package and found that the TargetFrameworkVersion node placed inside of a separate PropertyGroup node. After I had moved it out to the first PropertyGroup of the same arrayElement node, then reopened my package in Visual Studio again, issue was gone! So you can write a script to move TargetFrameworkVersion node into the proper place for now.
Varigence support team told me that a public preview release is coming late next week which will include a fix for that.
I've been developing UWP app until I got this error (picture below). I've searched for solution but I couldn't find anything. It doesn't even say which package is the incompatible. How can I find the incompatible package in my solution? Also is there any way to re-create project.json by automatically? I ask it because I changed something on project.json and broke it more.
Also I'm using VS2017 and I'm able to run project without issue. I just can't update package.
Thanks.
(github link for project if you want to look at it.)
I used your GitHub https://github.com/almorax/dota2-handbook-uwp project to troubleshoot the problem and looks like the problem is with the way the nuget package is referred in "Dota2Handbook" project. In other projects, you have used "PackageReference" way to refer the nuget package however in "Dota2Handbook" project you are using project.json to refer nuget package. When I changed "Dota2Handbook" project to use the "PackageReference" way then I was able to get the latest package.
Note: You will notice that "Dota2Handbook.Infrastructure" project already use the new way to refer Nuget packages
More details on PackageReference : https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files
What happened to me is that I have UWP projects that were made in VS 2015 and initially targeting Windows 10 RTM. These projects where updated to VS 2017 and to target Creator's Update. All worked fine, and all projects still used the original project.json style.
Then I tried to create a new Windows Runtime Component project and target Creator's Update initially. Targeting Creator's Update in VS 2017 causes the project to use the new PackageReferences project style. This produced the errors shown in the above question when I referenced the WinRT component from the UWP app.
Rather than converting the all of my legacy UWP project files to use the new format, I target the new UWP or WinRT Component library to Anniversary Edition (which uses the older project.json project style), then retarget to Creator's Update.
Of course, at some point updating the project file may be appropriate, just know that it will no longer be supported by VS 2015. Conversion steps are illustrated here.
I got my hands on Windows 8 machine and, willing to check out new Windows Runtime API, downloaded VS 2013 Express for Windows. WinRT offers possibility to code in HTML5/CSS/JS, but I'm interested in using TypeScript as an alternative to JavaScript when not coding for DOM. This possibility is outlined here, but only applicable to Visual Studio 2012 and not even to Express edition, as Web Essentials extension won't work there.
TypeScript web page claims that full support is built into VS 2013 Update 2 RC. However, while this update does install some new extensions and TypeScript gets installed in Program Files as well, it doesn't add TypeScript support to VS 2013 Express for Windows. I still don't get to create .ts file, let alone have it compiled from IDE.
Please note this is a different question from this one, which deals with VS 2013 for Web. I've checked the accepted answer there and it won't work. I'm interested in getting TypeScript to work with either VS 2012 Express for Windows 8 or VS 2013 Express for Windows. I'll also accept an answer pointing me to alternative IDEs for WinRT/Store Apps development, but web research tells me it's unlikely to happen.
Yes, it's perfectly possible to write a Windows Store app using TypeScript in the Express for Windows version of Visual Studio 2013. But unfortunately it isn't supported right out of the box. You'll have to modify the project file yourself.
This sounds harder than it is... I wrote a tutorial on how to this some time ago. It basically comes down to adding some xml to the project file, telling Visual Studio what to do with the .ts files.
After modifying the project the .ts files are compiled and even placing breakpoints inside the .ts files works.
I have a VS2008 Reporting Services project (database: SQL Server 2008 RC2). This project has been updated from VS2005/SQL2005.
I need to update the Report Viewer control to version 10.0.0.0. But when I install the Redistributable (http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=a941c6b2-64dd-4d03-9ca7-4017a0d164fd), it isn't added to the .NET-tab in the 'Add reference...' dialog!
I can see the Microsoft.ReportViewer 8.0.0.0 and Microsoft.ReportViewer 9.0.0.0 in the dialog, but no 10.0.0.0
I tried running uninstalls for everything ReportViewer related, and reinstalling the ReportViewer 10.0.0.0 control. But I still see both version 8 and 9 in the dialog, but no version 10!
Checking the GAC through Start->Run->Assembly I can see all three versions. I cannot remove 8 and 9 because they apparently are used by other programs...
This is driving me somewhat nuts...
What do I have to do to make this assembly available in the "Add Reference..." dialog in Visual Studio 2008??
Regards
Alex
OK, found a solution: Apparently VS2008 combined with ReportViewer2010 requires a little handy-work:
http://blogs.msdn.com/b/changliw/archive/2010/06/29/use-the-reportviewer-2010-control-in-visual-studio-2008-project.aspx
After I extracted the assembly DLLs from the GAC, I could add them to the 'Add reference...' dialog as described here:
http://www.csharp411.com/adding-assemblies-to-the-visual-studio-add-reference-dialog/
I hope this'll help another distressed soul! ;)
/Alex
Another possible cause of assemblies not showing in Add reference is the implicit target framework filtering. E.g.: Visual Studio 2010, .NET Fwk 4.0 target will filter assemblies targeting this particular fwk. To add Microsoft.ReportViewer.WebForms 10.0.0.0, I changed project's target fwk to 3.5, added the references and then switched back to 4.0.