This project is read-only.

10-17-2014 dev build

Rating:        Based on 5 ratings
Reviewed:  4 reviews
Downloads: 5485
Change Set: c16409b3360f
Released: Oct 17, 2014
Updated: Mar 9, 2015 by mousetraps
Dev status: Beta Help Icon

Recommended Download

Application NTVS Dev 2014-10-17 VS 2013.msi
application, 5620K, uploaded Oct 17, 2014 - 4934 downloads

Other Available Downloads

Application NTVS Dev 2014-10-17 VS 2012.msi
application, 5620K, uploaded Oct 17, 2014 - 551 downloads

Release Notes

An intermediate release with the latest changes and bug fixes.

Reviews for this release

It can take some time to work around some ux quirks, but after that is seems to be working fairly well. Just don't add large node_modules like lwip or the entire project will crash in VS. I ended up using edge.js and wrote my own image converter for under 11 kb. lwip image tools was 46 megs. Also don't include the node_modules folder in the project thinking that is needed to publish to azure website.
by Randallto on Oct 13, 2014 at 3:40 PM
Hi Randallto, we'd like to fix the issue you ran into with lwip, but can't quite reproduce it - would you mind providing more detail here?
Reply by mousetraps (N/A) on Oct 14, 2014 at 8:50 PM
look stable great addition to typescript
by vclteam on Sep 28, 2014 at 4:54 PM
The debugger is more stable and a number of small annoyances have been fixed. Thanks!
by nabog on Sep 16, 2014 at 9:18 AM
With VS2013 update 3 I'm now able to use this release to load my solution, successfully debug, and don't experience any crashes when performing this simple workflow. However performance in terms of CPU usage and memory usage is still bad (and I guess if left unchecked will lead to a crash with >2GB in use). Turning off full intellisense helps but still not great. Can I help by providing you with more information? --- Additional information --- I set a breakpoint and followed the code execution into a couple of our modules but VS2013.3 soon crashed with
by andrewbryson on Aug 28, 2014 at 12:51 PM
This is a known issue in the latest dev build. We hope to have a new dev build soon to address.
Reply by RickWinter (N/A) on Aug 29, 2014 at 12:35 AM