How do I open VS2013 NODEJS projects in VS2015? - node.js

I wanted to load some VS2013 NODEJS Console (Typescript) projects into the new version of VS2015. This was the error message..
"The Project Types may not be installed" indicates that VS2015, by default does not appear to be able to handle NODEJS console (Typescript) projects. Do I need to install NTVS for VS2015?

As it turns out the answer is yes, you must load the NTVS package (Manually) which you can find at CodePlex... Make sure you close all instances of VS first...

Related

Excel add-in Shared runtime configuration, webpack.config.js is not present in project

I created an Excel Add-in project few months back using Visual Studio 2019. Now I am facing some issues and came to conclusion that Shared Runtime might not be configured correctly. So I followed this tutorial to update manifest of the project.
https://learn.microsoft.com/en-us/office/dev/add-ins/tutorials/share-data-and-events-between-custom-functions-and-the-task-pane-tutorial
However after that It is mention to update webpack.config.js, but this file is not present in project. Even if I create a new project using VS2019, this file is not there. Can anyone guide me how to add this file like its location, contents etc so that I can add it and follow next steps to configure Shared Runtime correctly.
You need to use the VSCode with yeoman generator to scaffold an add-in project which uses webpack for bundling. For example, the Build an Excel task pane add-in page contains guides for Visual Studio and Yeoman generator (as a rule VSCode or WebStorm developers).
Reply from Rick Kirkham on Github page is below.
https://github.com/OfficeDev/office-js-docs-pr/issues/3568#issuecomment-1201573455
This tutorial creates an add-in project with Yo Office. That kind of
project runs in Node.js. WebPack is a tool for bundling multiple
JavaScript files into one. WebPack is only relevant to Node.js based
projects. Since you created your project in VS 2019, your project uses
C# or VB.NET on the server side and runs in an IIS server. WebPack is
not used in that environment. That's why there is no webpack.config.js
file. Whatever problems you are having with the shared runtime, you're
not going to solve it with WebPack.
Consider raising your problem on Microsoft Q&A. Be sure to
"office-addin-dev".
Alternatively, consider recreating your project as a Node.js project.
You can use this tutorial as a good place to start.

Angular 2 and Ionic 2 with Visual Studio

So, this may be a stupid question, and if so I do apologize in advance. But I can't seem to find any documentation on this anywhere at all. My goal is to create an Angular 2 project, with Ionic 2 within Visual Studio, but I do not want to utilize any .NET framework. Everything I seem to find either utilizes the .NET framework, or works completely outside of Visual Studio within a separate IDE and utilizing command line tools, as well as node.js and npm. I'm just curious if this was possible to do, or if node.js/npm is the preferred manner of doing things?
Use visual studios code for your IDE. It is the light weight version of visual studios. It also runs on all OS. After that install all your global projects from command line like ionic, ionic CLI, nodejs. I install nodejs because it automatically installs NPM. Then inside VS code you can open the integrated terminal and use the ionic CLI to create a project skeleton and get started. The whole process is very easy and quick. To answer your final question, NPM is the easiest and probably the most documented way to get started.
utilizing command line tools, as well as node.js and npm
I'm really curious to know how can you build Ionic app without node. You must use Node.
if node.js/npm is the preferred manner of doing things?
Absolutely YES. If you want,instead of npm, you can use other package manager like yarn.
You can still use the Visual Studio as the IDE if it is your preferred IDE. Even Visual studio has a GUI process to ease the process of building the node app, It still use Node under the hood.

Can I use ES6 modules in a Node.js application and debug it in Visual Studio?

I've tried building a basic node.js ES6 module test project in Visual Studio 2015. But I get build errors and cannot run or debug the application in VS.
Have I just came to the party too early?
If it's worth anything I have tried opening and building the project in both VS2013 (Update 3) and VS2015 RC.
I have installed:
Node.js 0.12.2
Node.js Tools 1.0 for VS2013
Node.js Tools 1.1 Beta for VS2015
Additionally, I have added Robert Penners () node.d.ts gist to get over the import syntax errors.
See: https://gist.github.com/robertpenner/7d48f184df1236c4fdca
I have uploaded the project for others to try: https://dl.dropboxusercontent.com/u/10159140/es6-modules-ts.zip
Node Tools dev here. Thanks for reporting this. Indeed, we support the ES6 typescript target type.
That said, I'm running into issues running your app in the command line altogether with the latest versions of both node and io.js, so this may be a level of ES6 support mismatch between all the components at play here... Have you managed to successfully run your app in the command line (without the debugger)? Otherwise it may be related to this discussion:
https://github.com/nodejs/io.js/issues/1000
Once you figure that out, be sure to set up your project with the right node.exe arguments (harmony flag and whatnot) in project properties, so Visual Studio knows how to run it too.
Hope that helps!
P.S. just an fyi - we've moved to GitHub now, so please post issues there (rather than on CodePlex) for the quickest responses.
https://github.com/Microsoft/nodejstools

I can't create a new node.js project with webstorm 9.0.1

I just installed the webstorm 9.0.1 trial windows version, and when I try to create a new project in the project type list I don't see any reference to node.js applications.
I see in all the documentation that node.js project template is supported.
I'm missing something?
thanks,
Luca
I know this is a bit late, but perhaps the boilerplate samples were removed from 9.01? I'm showing the same thing and came across this post regarding version 8 -
Webstorm IDE missing Node.js Boilerplate Project type
EDIT :
And omg, the issue was I didn't scroll down :) I don't see the boilerplate app referenced in the above link, but there is an Express seed app.
NodeJS project types missing in WebStorm
If you don't see any reference to Node.js, then you're most likely missing the plugin.
Go to File > Settings > Plugins and check if NodeJS is visible and checked. If it's not there, select Browse repositories, select NodeJS and Install plugin and restart your IDE.

Project is targeting frameworks not installed or are included as part of future updates to Visual Studio

I am attempting to convert the Microsoft.Health C# class library that is installed as part of the HealthVault SDK, using instructions provided here. After following these instructions, I get the following error when attempting to load the project into Visual Studio 2013.
"The project is targeting frameworks hat are either not installed or
are included as part of future updates to Visual Studio. See
http://go.microsoft.com/fwlink/?LinkId=287985"
Visiting the link takes me to .NET SDKs and Downloads. Once there, I have no clue on what needs to be done.
I do realize that one will have to leverage the Portable Class Library Contrib project to fill in some missing bits, especially code related to System.Security. This, I will deal with later.
Any one run into a similar problem?
Maybe so late but for those who have the same problem.
I had the same error in a project which was working perfect before updating VS2013 and finally after 3 hours looking for the source of the error I found that the error is about TargetFrameworkProfile.
In my case I sloved it like so:
Right click in the unloaded project in your solution and click Edit.
Find the TargetFrameworkProfile tag and set it as below:
<TargetFrameworkProfile>Profile78</TargetFrameworkProfile>
At a guess, this is because you need to specify the TargetFrameworkVersion and TargetFrameworkProfile properties in the project file. Compare the .csproj you are trying to create to a newly created PCL project file, and make sure that everything that's not specific to your project matches.
I ran into the same issue and got it resolved by installing the latest Visual Studio Update

Resources