VS2017 Community "Windows application packaging project" does not show - visual-studio

In my VS2017 community installation there is no option to create "Windows Application Packaging Project" as shown in Microsoft introduction. I'm not quite sure why it is like that? Because I installed .Net Framework 4.6.1 (see fig). Is that the Community version does not support packaging for Windows app?

Im creating a new answer instead of commenting because i dont have the required reputation.
I had visual studio 2017 version 15.9.15 installed but i still couldnt find the Windows Application Packaging Project, so i clicked modify on my version from the Visual Studio Installer and it turned out that i hadnt installed UWP development in the first place.

Related

Windows Installer for Office solution by using Visual Studio Community 2019

UPD: I found old article that I used a few years ago and followed me step-by-step with deploy using Windows Installer Deploying a VSTO Solution Using Windows Installer. Problem solved
I wrote a custom add-ins menu for Office using Visual Studio Community 2019. Now I'm trying to deploy it. In this article Deploy an Office solution by using Windows Installer they used VS2013 and InstallShield Limited Edition, which doesn't work with VS Community 2019. I installed Advanced Installer but in the Help section "Create a package to deploy an Office Add-In developed in Visual Studio" says "The following article uses options that are available starting with the Professional edition and project type." what means I need to upgrade free version to commercial.
Could you please recommend any other Windows Installer for Office solution for Visual Studio Community 2019? Or any step-by-step article how to deploy solution by using Setup Project in VS Community 2019?
I remember I tried to do some deploy in old version of VS a few years ago, but nowadays it seems more complicated. I just want to try and see if my add-ins work in another computer and then I'll think about commercial versions of VS or Installers
Thanks,
Elena
You can build the package using the free version of Advanced Installer too, but you will have to create all the registry entries (those related to your addin) manually and also the same for adding the files in the package, as documented in the MS article.
The wizard that you mention above does this automatically by reading the necessary info to make the configs from your Visual Studio solution.
Disclaimer: I work on the team building Advanced Installer.

Can I build a command line tool for Windows 7 with Visual Studio Community 2017?

I downloaded Visual Studio Community 2017 because I need to build a command line tool to perform some administrative tasks on Windows 7. Is this possible and if so, what project should I select?
When I create a new project I can not choose "Universal Windows" projects, because these are restricted to Windows 10. A project I can create is a Class Library (.NET standard), but I have no way of executing this as it is a library and won't run from a Main() method, nor am I able to add a Unit Test project, because that is only available for Universal Windows.
I installed a load of extra .NET framework versions, the Windows 8 jdk, I searched for project templates online, created a "Blank Solution" from "Other project types", etc
So the question is basically, how do I build anything that runs on Windows 7?
I am going to answer my own question again. I set up Visual Studio for "universal Windows platform" development, because it sounded suitable for the simple app that I wanted to build, but the universal Windows platform is all new and aimed at Windows 10. My bad. After I added ".NET desktop development" via the Open Visual Studio Installer I now have my beloved Console Application project.

Can't open an MVC3 project in VS2012

I just installed visual studio 2012 professional (with Blend) and now I can't open a .NET MVC3 web project. The project does not load and says it is incompatible, despite the fact that other developers working on the same codebase are using VS2012 with no issue.
Furthermore, when I go to Solution -> Add -> New Project, I don't see the option to add a web project that I did with VS2010. This makes me think that I am missing some kind of web developer setting, extension, or add-in, but I can't figure out how to install that.
How can I fix my visual studio (or project) setup to allow me to open this project?
You do not appear to have installed a web version of visual studio.
I'm guessing you installed the Express version of either the Windows 8 Edition (which creates Windows 8 apps) or the Windows Desktop version (or maybe Windows Phone version).
If this is the express edition, download and install the Web Edition. If this is a Professional or higher version, then you may not have installed the right components.

Windows 8 SDK Platform Toolset missing in Visual Studio 2010

I just installed .NET framework 4.5, the Windows 8 SDK, and the Windows 8 DDK on 2 different machines (one at home managed by me, one at work originally setup by IT) both with Visual Studio 2010 Professional SP1 already installed, and both running Window 7 Professional.
I had an old C++/Win32 application in Windows XP that used both the Windows SDK and DDK. I updated it for Windows 7 and Visual Studio 2010 project settings. However, it would not build because some of the SDK/DDK include and library files are new, and it couldn't find them with Platform Toolset set to "v100" in Visual Studio.
Manually adding the Include and Lib folders to the project made it build and run correctly.
Is there some way that I can add the newly installed SDK and DDK to Visual Studio 2010's "Platform Toolset" list? I thought it was supposed to do this automatically, but neither of the machines I use have it in their list after install and reboot.
After researching this quite a bit, I finally found a solution. It doesn't look like it can be added to "Platform Toolset" via any simple method, but at least you don't have to add the paths on every single project you want to use the API. This worked for me, and allowed me to build Microsoft's "USBView sample application" written for VS2012. The way Microsoft recommends (from the official Microsoft Visual C++ Team blog) is:
For a single project:
http://blogs.msdn.com/b/vcblog/archive/2012/03/25/10287354.aspx
This seems to work with the final SDK release as well.
To apply those settings across multiple projects:
http://blogs.msdn.com/b/vcblog/archive/2012/11/23/using-the-windows-8-sdk-with-visual-studio-2010-configuring-multiple-projects.aspx

no compatible version of visual studio net found on system

I have installed full version licensed Visual Studio 2010 Professional, .Net 4.0 on my system. Now I am trying to install Active Reports 6 on it and facing the error "no compatible version of visual studio net found on system". My Active Reports build is 6.0.1.1797.0.
So, do I need to install framework 3.5 before installing? I have not installed Service Pack for visual Studio for now.
Thanks.
Active reports 6.0.1797.0 does not support Visual Studio 2010. Active reorts 6.1.2577 or later supports Visual Studio 2010. And any how, Express edition of visual studio does not support active reports.
So my solution, enhances...I installed the later versions...but unfortunately I am getting some errors in my application because of Active reports version change as my application was made in previous version of Active Reports. So, what I did is, installed the latest version, uninstalled it and again installed 6.0.1797.0 version, and it was installed successfully and my application was also working fine.
#rapsalands...You are correct in understanding that support for Visual Studio 2010 started only after build 6.1.2577.0 was released. Also express edition of Visual Studio is not supported. The first thing to note here is that whenever you install/uninstall ActiveReports 6 from your machine, there should be no running instance of Visual Studio as it affects proper integration of ActiveReports with itself.
Also the errors which you were getting are more likely appearing because of the incorrect references in your project. Whenever you open an existing project after upgrading ActiveReports build, you should remove all the ActiveReports references from the project, re-add them (making sure they point to the version currently installed) and finally rebuild your project.
I think you can also check the blogs for ActiveReports as you might find some useful information about different topics there.

Resources