Within a restricted web development environment my team has the following installed:
With this suite of tooling I’d like to attempt at working with an existing AngularJS/ASP.NET MVC 5+ portfolio consisting of several web applications.
- Visual Studio 2015 Professional (Release Version, not Update 3)
- Typescript 1.6 (via default install options of Visual Studio 2015 Professional)
- Note; a later version of Typescript (3.0x) can be made available via path variable but this is the version that is integrated via Typescript installation.
- Node JS 10.4 (via unzipping to directory and user PATH variable)
- NPM 6.1 (via unzipping to directory and user PATH variable)
- NPM Task Runner (Visual Studio 2015 extension)
- Webpack Task Runner (Visual Studio 2015 extension)
My team can build the ASP.NET/C#/MVC 5+ middleware and backend components just fine; the problem is that there is essentially little to no Typescript debugging/IntelliSense/etc. experience available to them.
With Typescript 1.6 built into the Visual Studio 2015 Professional IDE, said constructs do not recognize the new Typescript methods/etc. that later versions of Typescript added. Therefore, as later libraries of Angular evolved over the course of 2+ years the built-in tooling within Visual Studio has become woefully out of date.
Because of this, local front-end development is painful to the point of being extremely time consuming and error-prone. If this were just one or two files the instruction would be to look past but with hundreds of files the experience is extremely degraded and the fear is said experience would lead to poor productivity and eventual bugs/defects leaking into upper environments (staging/production) due to the poor tooling.
The following challenges persist in this environment which makes an easy resolution path difficult:
- No administrative rights on local development machines
*Any new tooling must come from stand-alone executables or configurations
- Training of Existing Staff
- Any solution must be scalable such that new development teams can utilize
Current (Unsustainable) Solution
The way my team is resolving this now is via usage of remote desktop (via Windows RDP) into a specifically tailored remote server. However, said system is being decommissioned due to organizational policies. Therefore, future development must be performed via local installations.
My Current Path of Resolution
At this current point in time, I am looking into putting forward Visual Studio Code (via standalone executable and associated User-PATH variable edit) as an alternative to edit the Typescript-based files and using Visual Studio 2015 Professional for everything else. However, I know that the debugging/editing experience for this would not be ideal.
Any advice welcome. Thank you for your time.
- Is there a way for Visual Studio 2015 Professional to utilize a different version of Typescript for the editing experience without installing a newer version of the Typescript SDK?
- If not; is there a way to disable editing of Typescript files within Visual Studio 2015?
- I have tried to alter the “csproj” project files by setting the following to no avail.
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.Default.props" Condition="True" />
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.targets" Condition="True" />
- Are there any alternatives to the above worth considering?