| T O P I C R E V I E W |
| dcsoft |
Posted - Sep 26 2013 : 09:15:48 AM
Hello,
The VA Outline remains empty for .JS and .XML files in:
* VA 10.8.2001.0 (built 2013.09.20)
* VS2013 RC
Thanks,
David |
| 8 L A T E S T R E P L I E S (Newest First) |
| Juxta |
Posted - Nov 12 2013 : 4:14:58 PM
quote:
Originally posted by feline
We are not dropping JavaScript, just not promoting it so clearly at the moment, while we focus on C++ and C#, which are the languages most of our users are working with.
I believe if you ask, you will find this is changing. You are heading in the wrong direction. Visual Studio is clearly stepping up efforts for ease of use with JavaScript in Visual Studio. Many of my colleagues who are native VS users are increasingly needing to use VS to edit and manage JavaScript in solutions. If you turn off support, you are just encouraging a drift away from VS in the more web/javascript oriented development.
I have seen folks turning to Eclipse and other editors because of Microsofts sluggishness in this area, although they are improving, surely its not good for your business to ignore this area. You could make it much easier and add great value to VS as a HTML/Javascript/C#/C++ integrated environment.
Please resume you focus on JS. Im sure it will be widely appreciated. (and save us from Eclipse) |
| feline |
Posted - Oct 29 2013 : 5:45:40 PM
We are not dropping JavaScript, just not promoting it so clearly at the moment, while we focus on C++ and C#, which are the languages most of our users are working with. |
| Juxta |
Posted - Oct 28 2013 : 7:31:30 PM
Please keep Javascript. Not sure about others but all at my place of work use all javascript/c#/c++ and we would hate to see support depreciated. This is where we live these days.
WCF back end/ Javascript front. |
| feline |
Posted - Oct 01 2013 : 12:30:47 PM
This is something we are going to be monitoring. VA is still active in C# by default, without needing to edit the registry.
There does seem to be a shift away from C/C++, but there is also improved C/C++ support in VS2013, suggesting a shift back again. We are working hard to make sure that VA continues to be useful and valuable to as many programmers as possible, and hopefully doing a good job of this. |
| dcsoft |
Posted - Sep 27 2013 : 6:30:30 PM
Thanks for the explanation. I might suggest adding an easier way to enable all file types instead of editing the registry and restarting. Also, perhaps a large part of your customers are like me who started out in C/C++ but have moved to C# and JavaScript, etc. as these have taken over the Windows 'ecosystem', in large part displacing C/C++.
Thanks,
David |
| sean |
Posted - Sep 26 2013 : 8:13:41 PM
There are a couple of parts to the reasoning:
1) new versions of Visual Studio have new features so VA starts with a clean slate as far as its core settings go (some VA settings default differently depending on which version of Visual Studio you are using).
2) our focus is C/C++ and we stretched ourselves too thin trying to support other file types. We don't plan on removing support for the other file types, but we don't really want new users to see what problems we caused for ourselves there. |
| dcsoft |
Posted - Sep 26 2013 : 1:45:17 PM
Thanks Sean! Working now.
IMO, the new behavior is not obvious or expected.
Thanks,
David
|
| sean |
Posted - Sep 26 2013 : 11:31:20 AM
VA has new default behavior when first installing (or installing into new versions of Visual Studio): active only in C/C++/C# files.
The old behavior can be enabled via modification of a registry value:
http://docs.wholetomato.com?W326 |
