VS 2017 and Microsoft Cognitive Toolkit 2.0 RC3 (CNTK) - cntk

Can I compile Microsoft Cognitive Toolkit 2.0 RC3 (CNTK) with VS 2017 Preview?

VS2017 does not work.
CNTK needs VS2015 update 3.
2015-1 or 2 also does not work.
Installation takes time so better to check.
To check Visual studio version
click Help => About Visual studio.

I don't think anyone has tried. It's probably OK, except if you want to compile the GPU stuff. Nvidia is currently not listing Visual Studio 2017 as a supported platform.

Related

How do I force Visual Studio to make this project compatible with VS 2022?

I installed VS 2022 Community and am trying to work on a project that was developed on VS 2008 Pro. VS is giving me this report:
How do I force VS to make whatever upgrades it needs in order to run this program? I can provide more info if needed.
MS in their wisdom, dropped support for the Setup & Deployment project, can't remember when exactly, then after a bit of an uproar re-instated it through the Visual Studio marketplace https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2017InstallerProjects
Since your project has a file .vddproj, it might be a Smart Device CAB project.
It is not supported by later versions of visual studio.
It is recommended that you open it with VS2008.

RDLC and Visual Studio 2022

We started using Visual Studio 2022, but after few days we'v got this terrible news:
VS2022 doesn't support RDLC designer.
Is there a workaround?
Sure we can continue to use VS2019 in parallel, but it's too uncomfortable.
Ok, we have just found this thread:
Developer Community Visual Studio RDLC design in 2022
We'll keep it monitored, but at the moment they don't have release a new tool.
A workaround seem to be this (quoted in the link above):
A workaround until the designer is officially supported is to download Microsoft Report Builder and use it in editing your reports, Demo: https://youtu.be/3Wss8bvzjiE
EDIT:
Released for 2022!

Universal Windows App Visual Studio 2015 Community no designer, no controls in toolbox, no properties

I am using Visual Studio Community 2015 to create Universal Windows App.
I am facing following problems-
1. No designer view.
2. No controls in toolbox.
3. Property window don't show any properties of control.
4. No phone emulators are shown after installing EmulatorSetup.exe
Visual Studio Installed Components are as follows
Microsoft Visual Studio Community 2015
Version 14.0.24720.00 Update 1
Microsoft .NET Framework
Version 4.6.01055
Installed Version: Community
Visual Basic 2015 00322-20000-00000-AA136
Visual C# 2015 00322-20000-00000-AA136
Visual C++ 2015 00322-20000-00000-AA136
Application Insights Tools for Visual Studio Package 4.2.60128.3
ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11106.0
ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
Common Azure Tools 1.5
JetBrains ReSharper Ultimate 10.0.2 Build 104.0.20151218.120627
JSLint.NET for Visual Studio 2.2.0
Microsoft Azure Mobile Services Tools 1.4
NuGet Package Manager 3.3.0
PreEmptive Analytics Visualizer 1.2
SQL Server Data Tools 14.0.50616.0
TypeScript 1.7.6.0
Visual Studio Tools for Universal Windows Apps 14.0.24720.00
Web Essentials 2015.1 1.0.209
I have had the same problem and the only way I have got the designer to work is (and this should work if build 10240 is acceptable for your development):
Open your project
Go under "Project" to "Properties"
Select "Application" on the left and change BOTH the target version and the min version to "Windows 10 (10.0; Build 10240)
Once you do that the XAML designer will start working again. I've had to do this on 4 different workstations and it's worked everytime.
As to why build 10568 doesn't work? Got me, agile development, will be fixed in a patch? :p
I had the same problem and could not change BOTH versions to Build 10240 as the Application listbox only showed 10586 in Properties/Application. I thought I could arrange that by editing the .csproj file, which is XML after all, but any change there makes all files in the Solution Explorer immediately unavailable. Then I noticed (running Winver.exe) that my W10 still shows build 10240 despite regularly (but not automatically) running Windows updates. Despite multiple solutions tried, this didn't change. I finally used the MediaCreation Tool to download a new Windows 10 on a USB stick and reinstalled Windows 10, preserving apps and data. And now I am really on 10586 ...and the Design mode shows again when I open my project.
I hope this helps a few!
If you are looking for the SSIS toolbox, click SSIS tab, then SSIS Toolbox.

WIX: detect if visual studio 2013 installed

All we know about this charming way of detection Visual Studio path and others: wixvsextension
Also we know that VS2013 is supported in latest WIX builds.
But Visual Studio 2013 was released and I cannot find any documentation about VS2013_ROOT_FOLDER and VS2013_IDE_VWD_PROJECTSYSTEM_INSTALLED.
Are they implemented but not documented?
Yes, they're implemented but not documented. That's a bug.

Board Support Package

Currently our BSP is built using Visual Studio 2005. I would like to update this to use VS 2010 at the very least, preferably 2012. I have not been able to find anything that will allow me to do this. I tried to upgrade the project to VS 2008, but it failed to load the project. I was wondering if anybody had some ideas or could at least point me in the right direction.
Visual Studio 2008 does support the Platformbuilder Plugin and creating Applications for Win CE, however the import wizard is not perfect, you may need to change some settings by hand.
Visual Studio 2010 does not support creating BSPs or applications for Win CE.
Visual Studio 2012 will support creating of BSPs and applications for Windows Embedded Compact 2013.
It also includes a new faster version of the .Net Compact Framework.
http://blogs.msdn.com/b/windows-embedded/archive/2012/11/14/windows-embedded-compact-v-next-uncovered.aspx
http://channel9.msdn.com/Events/Visual-Studio/Visual-Studio-2012-Virtual-Launch/Visual-Studio-2012-support-for-Windows-Embedded-Compact