Unable to install lync 2013 sdk with VS 2013 - lync-server-2010

I am using VS 2013 and need to reference the Lync 2013 SDK. The install fails with:
Microsoft Visual Studio 2010 SP1 or higher not found
Is there any work around or do I have to downgrade to VS 2012?
Thanks,
Bill

I got it solved.
You can fix it by installing WinRAR and then right-clicking the .EXE file (the installer), extract it, and then run the 64 bit setup file. It installs to Program Files from where you can just reference the DLLs.

Related

CMake Error: Could not create named generator Visual Studio 16 2019 in flutter

I want make windows app with flutter.so I installed Visual Studio 2019 with desktop development with c++.
when I use flutter run -d windows I see
this error
I also installed latest version of CMake(version 3.20.0-rc4) and version of my Visual Studio is 16.0.0
I can tell from that image you aren't actually running cmake 3.20
Because Ninja Multi-Config isn't being listed as a generator. That flutter command you used isn't using the CMake you installed on your system. Or you need to restart your machine.
I find the problem.
for resolve this problem I have 3 different way and I'm not sure which one resolve this problem.
first uninstall CMake
if you run flutter doctor and don't see any error create another flutter project with flutter create <project_name> and run that with flutter run -d windows
I was using Windows SDK version 10.0.17763.0 I update that to latest version(10.0.19041.0)
I update my visual studio 2019 to latest version(16.9.1)

not able to install SSDT for visual studio 2017 professional

Need your help
I have successfully installed VS2017 on my computer .
But when I tried to install SQL server data tools 15.6.0 or 15.5.1 it gives me error as below :
Setup failed
The configuration registry key could not be opened(0x800703F3)
Thanks All!!
The latest version (15.6) of SSDT is incompatible with the latest version (15.7) of Visual Studio 2017. You currently have two choices:
Wait for an updated version of SSDT or VS2017 to be released, or
Completely uninstall VS2017 and install an older version.
If you want to go with option 2, do the following:
Run this command: C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe -f
Download and install version 15.6.7 of Visual Studio (link to the Community edition)
Download and install SSDT 15.6.0
This info was taken from a post on the Visual Studio Developer Community forum.

MSBuild opens a new instance of Visual Studio

We have been using Visual studio 2010 - 2013 on the build server using the following MSBuild command so far:
Set msBuilder=%windir%\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
However recently we moved to VS 2015, and had to uninstall all other VS versions (for saving space), and used the following build location (partially also to cater compilation of C# 6.0 features):
Set msBuilder =%ProgramFiles(x86)%\MSBuild\14.0\Bin\MSBuild.exe
This seems to work for most of the VS Solutions we have,however for one particular VS solution, when we execute this line:
Set doSolutionBuild=%msBuilder% MySolution.sln /t:clean;Build /p:Configuration=Release;Architecture=x86;Platform=x86 /v:n
it opens and instance of VS 2015 of the same project on the build server and the build process just hangs there in the command prompt.
Can anyone explain how we could resolve this?

Error in upgrading report server project in Visual Studio 2017

I recently have attempted to migrate a solution created and developed in Visual Studio (VS) 2012 to VS 2017.
I've managed to migrate all projects of my solution except for a Report Server Project. When I try to open my solution in VS 2017 I get the following message:
I click on Yes and VS automatically upgrades the project file (this is a file having the extension .rptproj)
When I now try to build the project I get the following error message:
Error Copying file Reports\Report\Project1\MyReportProject.rptproj.user to
obj\Debug\AspnetCompileMerge\Source\Reports\Report
Project1\MyReportProject.rptproj.user failed. Could not find file
'Reports\Report Project1\MyReportProject.rptproj.user'
I thought the upgrade would be performed transparently. Am I missing something? Is there any extra step I should take in order to do the upgrade?
Note: I've already downloaded and installed the latest version of Microsoft Reporting Services Projects .vsix package.
You can try the latest msbuild.exe for SSRS is here.
This includes steps of up-gradation of SSRS for both VS15 and VS17.
Once you install the latest update, depending on which version of Visual Studio you’re using, the new files enabling MSBuild for your projects will be installed in different folder path:
In Visual Studio 2017, it’ll will be a nested folder in your Visual Studio folder hierarchy. For example, the location with the Community Edition is in the Community folder:
Edit 1:
Try these steps:
1) Close Visual Studio - 17
2) Open VS-17 Installer
3) Try to install the SSDT workflow as:

Silverlight 5 Tools For Visual Studio - troubles with install

I have Visual Studio 2010.
I installed Visual Studio 2010 SP1.
When I'm trying to install Silverlight 5 Tools, I get error below:
Setup has detected that Visual Studio 2010 Service Pack 1 is not
installed, which is required to install the following product. Please
install Visual Studio 2010 Service Pack 1 and then retry. Visual
Studio 2010 Service Pack 1 is available at http://go.microsoft.com/?linkid=9764693.
Setup has detected that Visual Studio 2010 Service Pack 1 is not
installed, which is required to install the following product. Please
install Visual Studio 2010 Service Pack 1 and then retry. Visual
Studio 2010 Service Pack 1 is available at http://go.microsoft.com/?linkid=9764693.
What I'm doing wrong?
It looks like the tools aren't properly detecting that SP1 has been installed. I'd try the following steps to fix it
Reboot the computer. It's possible the SP1 install needs a final reboot to complete
Repair the Visual Studio install
Reinstall SP1. If Silverlight thinks it's not installed perhaps it didn't complete properly and another round will fix it.
Sorry, these aren't great solutions but this is what I would be trying on my machine

Resources