We updated our SQL Server from Standard to Enterprise. All my solutions were originally built in Visual Studio 17 (SSTD) and deployed as VS 8, 12, 14. I updated one of my reports and deployed it as VS16. The report worked at first, then became really laggy. All other reports were working fine. I attempted to open the solution using Blend, but it indicated it was incompatible. When I attempted to reopen the solution using VS 17 (SSDT), it indicated the same error (incompatible). Now I am unable to open any solution using VS 17 (SSDT) nor Blend. They all indicate that they are incompatible. I noticed that the Microsoft Reporting Services Projects extension (Ver 2.5.9) was disabled. I re-enabled it, but it did not resolve the issue. Not sure what to try next...…..
Update: After trying a multitude of possible solutions that worked for others, this was a really simple fix (which I found by accident). If anyone receives an 'incompatibility', I would definitely suggest this, prior to any other attempt.
I opened VS 17 (SSDT) and attempted to load my solution.
In the Solution Explorer, the Solution is listed with (incompatible) in brackets.
Right Click on the Solution Name and look for the 'Resolve Issues' option.
That was it. Resolved!
Hope this helps anyone who receives the same issue.
Related
We are using node to build the LESS files in our .NET application.
To do so, we have prepared some stuff to support that easier for all the developers. In the end we have a node version in the source control.
Everything works fine for everyone except one developer that has joined our team in the last days.
Whenever he tries to run the stuff, the CSS files are just empty.
To find the reason we have tried to skip all the stuff around and call node with the less package directly from console. This is working as expected on my PC but there is no output at the affected developers PC.
Also when we are using a path to not existing package there is no output.
On my PC there is an error logged into the console, the affected developer does not get any output.
The only parameters that seems to work are "-h" and "-v"...
As we could not find any usefull hints in the internet, maybe anyone having an idea what can be reason?
Windows-configurations, ....
Finaly we could solve the problem:
Don't ask why but uninstalling Visual Studio 2019, installing VS 2017 and installing 2019 again solved the issue somehow... everthing works as expected.
Reinstalling VS 2019 alone did not solve the problem before.
Maybe a hint in case someone else comes to this question with the same issue:
The reason for going to VS 2017 where different issues with ReSharper as well. Mainly performance issues of VS when ReSharper was active, but some functional issues too. This issues where gone as well after that.
It seems there was something broken with the VS2019 installation that was not repaired by uninstalling and reinstalling VS2019 but by VS2017...
I am facing the below errors when trying to install any type of MS SQL Server on Windows 10 operating system. There seem to be a common problem/error in all of the cases (i.e. An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32") for which I could not find any workable solution in earlier related posts or other sites (quora, microsoft support etc). This is similar to iTunes installation error but the workaround for that particular solution did not solve my problem. Screenshots provided in the following arrangement:
MS SQL Server Management Studio 2016
MS Visual Studio 2015
Somehow, I have been able to solve the issue. THANKS 3N1GM4!! You did point me to the right direction! Fiddling a bit here and there solved the issue. Listing down the steps as reference to other users facing the same:
Quoting 3N1GM4: "Go to C:\Windows\Installer and search for *.msi, then add the Comments column to the Explorer window and find the file for Microsoft Visual C++ 2005 Redistributable"
Right click and uninstall
Download vcredist_x86.exe
Extract content of vcredist_x86.exe using command prompt, which will result to the VCREDI~3.EXE being extracted. Ref: (http://www.itninja.com/software/microsoft/visual-c-2005-redistributable/8-1662)
Once again, extract VCREDI~3.EXE following the steps in above link, which will result to i) vcredis1.cab and ii) vcredist.msi being extracted.
Now, run and install vcredist.msi
Note: Not sure if steps 5 & 6 were redundant but I went through with them anyway. Installing vcredist_x86 directly after step 3 may also solve the problem.
Once again, I would like to thank 3N1GM4 for this ingenuity!
I'm afraid I know the answer to this already, but I'm hoping someone can point me in a better direction. I just finished developing a large ETL project using VS2013. My dev machine has SQL Server 2012 installed, and everything works perfectly executing from within VS. However, I just went to deploy the project to another device running SQL Server 2012, and got a version error.
I thought if I could open the solution in VS2012, the packages might recompile correctly. However, I can't open them in VS2012 due to version errors again ("version can't be lower than current version" error). I'm pissed because everything worked fine in development with the VS2013/SQL2012 combo, but now suddenly it's no good?!?
Can someone please help me figure out how to get these packages downgraded to work with VS2012/SQL2012? There are only a few script tasks involved if that makes a difference. Mostly it's just basic SSIS tasks and data flows.
Thanks.
I found a workaround how you can "downgrade" your SSIS 2014 packages to SSIS 2012. I wrote it on my blog here:
http://vaniecastro.com/2015/02/26/how-to-downgrade-sql-server-integration-services-2014-packages-to-2012/
The idea is that you need to manually modify the XML file, change the PackageFormatVersion and replace ExecutableType property and componentClassID attribute values to use the DTSX2 Version 2012/01 values instead of the DTSX2 Version 2014/01 ones.
You can try using Visual Studio 2015 SSDT Preview. This now allows you to choose which version of SQL Server you want to target, including SQL Server 2012. I successfully downgraded my packages from VS 2013 / SQL Server 2014 to SQL Server 2012 this way.
https://msdn.microsoft.com/en-us/mt429383.aspx
Once the shell is installed, go to the Project menu=>Project Properties=>Configuration Properties=>TargetServerVersion and choose 2012.
I have been sent a working project from a coworker to start learning Visual Studio. The project is under version control, however I don't want to have access to final customer product. So when I try to open the solution file I first get a message that the project is under source control:
"Team Foundation Server Version Control
The solution you are opening is bound to source control on the following Team foundation Serer:
http:// . Would you like to contact this server to try to enable source control integration?"
[yes] [no] [help]
I press no, then I get an error:
"The solution appears to be under source control, but its binding information cannot be found. Because it is not possible to recover the missing information automatically, the projects whose bindings are missing will be treated as not under source control."
[ok] [help]
I proceed and press ok, and another message pops up:
"projectname\projectname.tsproj: The application which this project type is based on was not found. Please try this link for further information: http://go.microsoft.com/fwlink/?prd=12395&pver=11&sbp=ProjectTypeDeprecated&plcid=0x409&clcid=0x409&ar=MSDN&sar=ProjectCompatibility&o1=B1E792BE-AA5F-4E3C-8C82-674BF9C0715B"
My coworker tells me he sent the whole project, so I can't figure out why I cant get visual studio to open it. I am new to visual studio, but I have some programming experience.
Any help is much appreciated.
Thank you
It is doubtful that version control has something to do with your problem. There are two possibilities I could think of:
Your coworker uses full version of VS2012 and you are now having problems due to the fact that Visual Studio Express comes in two main flavours - Web and Desktop. It is unable to load Web(or Desktop) project because it just does not have any tools to work with it. Ask your coworker whether they mix web and desktop in their solutions. If it is so you should either use full VS or be given a reduced set of projects.
Nearly the same - your coworker uses some very old or very new version of particular project type (something like ASP.NET MVC that(as I remember) has different project type for each version). Again ask your coworker if it is so. In this case you will just have to install the needed templates and SDKs.
P.S. I was unable to open your link - it opens microsoft.com/default(maybe due to some regional problems). Search by key words brought to me similar problem for VS2010 http://connect.microsoft.com/VisualStudio/feedback/details/728847/could-not-open-vs2010-solution-with-mvc-project - may be it could help you more specifically.
When I start up VS 2012 RC I get the following loading error message:
The 'SqlStudio Profile Package' package did not load correctly.
The problem may have been caused by a configuration change or by the installation
of another extension. You can get more information by examining the file
'C:\Users\User\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.xml'.
I also have SQL Server 2012 RTM installed.
What can I do to get rid of this warning?
Open Control Panel
Open Programs and Features
Locate all items named “Microsoft SQL Server 2012 Data-Tier App Framework"
Note: There might be up to 4 such instances all with the above name
Right click each of them and select Repair
That should solve this issue.
Janaka solution worked for me.
But if you do not want to lose your VS configuration, remove only the file :
Microsoft.VisualStudio.Default.cache
from the folder
%UserProfile%\AppData\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
Hope it helps.
Remove the following folders.
C:\Users\UName\AppData\Roaming\Microsoft\VisualStudio\10.0
C:\Users\UName\AppData\Local\Microsoft\VisualStudio\10.0
See this
It turns out that (in my case), the Data Tools installer has a bug whereby you end up with a registry full of:
Microsoft Visual Studio 11.0Common7
...paths, when it should be:
Microsoft Visual Studio 11.0\Common7
Fixing all the values and keys fixes the problem (for me).
(ps: no other solution in this thread worked for me)
Just reinstall SQL Server Data Tools (SSDT)
I had to run VS as an administrator in order to clear this issue.
Problem: The 'SqlStudio Profile Package' package did not load correctly.
Proven Solution:
Removing Microsoft.VisualStudio.Default.Cache fixes the problem outlined above. It worked!