Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Feature Requests

Visual Studio 2017 & "Open Folder"

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
MrDoomMaster	Posted - Nov 22 2016 : 2:04:10 PM I'm sure that Whole Tomato has some sort of pre-release announcement planned for the support of Visual Studio 2017 (also known as VS 15 2017?). However, I'm specifically interested in learning about any plans you guys have for the "Open Folder" functionality introduced. I really love this feature since it doesn't require me to explicitly manage visual studio solution + projects, because of the CMake integration. Does this drastically change Visual Assist integration? Will you support normal VA behavior when opening folders in VS 2017? Will indexing expand to Java files, CMake scripts? There is a TON of really cool stuff you guys could do with this new functionality and I really won't be able to use VS 2017 without VA working with open folder support. I'm very excited to learn more! [edited to move to Visual Assist forum]
7 L A T E S T R E P L I E S (Newest First)
sean	Posted - Mar 24 2017 : 10:22:24 PM case=104738 was opened for this problem. case=104738 is fixed in build 2212, however settings in cmake folder-based projects are not yet supported.
sean	Posted - Mar 21 2017 : 3:00:11 PM It failed for me the first time I tried to open a folder after updating to 15.0.26228.9 D15RTWSVC, but I haven't been able to repro after that one time -- it works 100% now. Please capture a va log (https://support.wholetomato.com/default.asp?W305) and send it in at http://www.wholetomato.com/support/contact.asp with TOPIC_ID=12804 in the subject.
MrDoomMaster	Posted - Mar 21 2017 : 1:50:02 PM Here is my version info: Microsoft Visual Studio Professional 2017 Version 15.0.26228.9 D15RTWSVC Microsoft .NET Framework Version 4.6.01586 Installed Version: Professional Visual Basic 2017 00369-60000-00001-AA965 Microsoft Visual Basic 2017 Visual C# 2017 00369-60000-00001-AA965 Microsoft Visual C# 2017 Visual C++ 2017 00369-60000-00001-AA965 Microsoft Visual C++ 2017 ASP.NET and Web Tools 2017 15.0.30223.0 ASP.NET and Web Tools 2017 Common Azure Tools 1.9 Provides common services for use by Azure Mobile Services and Microsoft Azure Tools. JavaScript Language Service 2.0 JavaScript Language Service KofePackagePackage Extension 1.0 KofePackagePackage Visual Studio Extension Detailed Info Microsoft MI-Based Debugger 1.0 Provides support for connecting Visual Studio to MI compatible debuggers Microsoft Visual Studio VC Package 1.0 Microsoft Visual Studio VC Package NuGet Package Manager 4.0.0 NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/. Visual Assist For more information about Visual Assist, see the Whole Tomato Software website at http://www.WholeTomato.com. Copyright (c) 1997-2017 Whole Tomato Software, Inc. Visual C++ for Cross Platform Mobile Development (Android) 15.0.26228.00 Visual C++ for Cross Platform Mobile Development (Android) Visual Studio tools for CMake 1.0 Visual Studio tools for CMake
sean	Posted - Mar 21 2017 : 12:56:34 PM It works for me in the version that I have (15.0.0-RTW+26228.4) -- but now there is another update available. I'll check it out today...
MrDoomMaster	Posted - Mar 21 2017 : 12:02:07 PM Just wanted to share that on build 2210 of VAX, it doesn't seem to be parsing or updating symbol index when opening folder instead of solution. I'm running on the official release of VS2017 Professional. Open file in solution, for example, doesn't show any results.
sean	Posted - Nov 30 2016 : 10:49:25 PM Build 2116 supports VS2017RC. Folder-based solutions aren't working quite as well in the RC than in earlier Preview releases. The system include paths aren't being populated properly. After you open a folder, check to see if the "stable include files" list on the C/C++ Directories page of the VA Options dialog is reasonable. You may have to switch Platform from Win32 to Custom and manually add system include paths to the list.
sean	Posted - Nov 23 2016 : 5:28:39 PM Visual Assist will support folder-based solutions in VS2017 but that does not affect the parsing of unsupported file types. Open File in Solution will work as you would expect. Find Symbol in Solution works as you would expect for symbols defined in files types that we currently support.

Snitz Forums 2000