Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 #include intellisense does not work with C++ nuget
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

barryl72
Junior Member

15 Posts

Posted - May 09 2014 :  10:47:45 AM  Show Profile  Reply with Quote
Steps to reproduce:

* In VS2013
* Create a win32 exe hello world project.
* Right click on project, and manage nuget references.
* Add expat, or zlib for example.
* Type '#include <z'
* Nothing happens.
* Disable Visual Assist.
* Type '#include <z' VS built-in intellisense works.

Additionally, as Visual Assist doesn't parse the header, you can't use VAX's go to definition.


Visual Assist switched on:




Visual Assist switched off (using VS native intellisense):



I'm running the latest beta, with everything else switched off in VS2013.

feline
Whole Tomato Software

United Kingdom
15984 Posts

Posted - May 10 2014 :  9:02:48 PM  Show Profile  Reply with Quote
Unfortunately this is a known problem:

case=79296

we are still trying to work out how to detect the extra include directories that nuget is adding. For now, if you only have a few projects using nuget then the best solution for now is to manually add the nuget directories to the projects additional include directories.

zen is the art of being at one with the two'ness
Go to Top of Page

barryl72
Junior Member

15 Posts

Posted - May 12 2014 :  02:20:19 AM  Show Profile  Reply with Quote
Thanks.
Go to Top of Page

barryl72
Junior Member

15 Posts

Posted - May 12 2014 :  05:16:13 AM  Show Profile  Reply with Quote
Is there a way to disable VAX's include intellisense?
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
15984 Posts

Posted - May 17 2014 :  5:56:59 PM  Show Profile  Reply with Quote
Apologies for the slow reply. Turning:

VA Options -> Listboxes -> Get content from default Intellisense

on gets you most of the way there. Can you please try this and see how much this helps? With this set, what problems are you still seeing?

zen is the art of being at one with the two'ness
Go to Top of Page

barryl72
Junior Member

15 Posts

Posted - May 29 2014 :  07:20:53 AM  Show Profile  Reply with Quote
Hi @feline - sorry for the even slower reply!

It appears that I already have that option set, and the results are still the same as shown in the screenshots above.

As far as I can tell, NuGet inserts an 'import project' directive, into the .vcxproj that includes a .targets file from the NuGet package. That in turn, is just an xml build with further msbuild (?) directives, including this:

<AdditionalIncludeDirectories>$(MSBuildThisFileDirectory)../..//build/native/include/;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>

Do you parse those things?



Go to Top of Page

feline
Whole Tomato Software

United Kingdom
15984 Posts

Posted - May 29 2014 :  3:46:42 PM  Show Profile  Reply with Quote
Interesting, thank you for the information. Our developers are currently looking into adding NuGet support, the trick is working out something solid and reliable, release worthy. I don't currently have an estimate for when this will be done, it partly depends on what they find, but hopefully this will appear sooner rather than later.

zen is the art of being at one with the two'ness
Go to Top of Page

barryl72
Junior Member

15 Posts

Posted - Jun 02 2014 :  10:32:18 AM  Show Profile  Reply with Quote
@feline - thanks. Getting this working would be a big help for us. If you have anything you need testing, please let me know.
Go to Top of Page

sean
Whole Tomato Software

USA
2641 Posts

Posted - Jun 02 2014 :  2:15:56 PM  Show Profile  Reply with Quote
@barryl72 Do you use the default repository directory ("packages") or do you customize it using your nuget config file?
Go to Top of Page

barryl72
Junior Member

15 Posts

Posted - Jun 03 2014 :  01:22:04 AM  Show Profile  Reply with Quote
Hi @sean - we use a NuGet.config file at the same level/folder as our solution, which then places the packages in a folder at the same level. The contents (for us, at least) is just:


<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <config>
    <!-- See http://docs.nuget.org/docs/reference/nuget-config-file for more detail. -->
    
    <!--  CUSTOM PACKAGE PATH  -->
    <add key="repositoryPath" value="packages" />	
    
    <!-- This prevents people accidentally pushing packages. -->
    <add key="DefaultPushSource" value="http://" />
  </config>
  <packageSources>
    <add key="TeamCity" value="http://teamcity:8070/guestAuth/app/nuget/v1/FeedService.svc/" />
    <!-- Once you add a custom feed NuGet now ignores the official feed so we have to add that as well -->
    <add key="NuGet official package source" value="https://nuget.org/api/v2/" />
  </packageSources>
</configuration>

Go to Top of Page

sean
Whole Tomato Software

USA
2641 Posts

Posted - Jun 03 2014 :  01:39:11 AM  Show Profile  Reply with Quote
I believe that is the default name and location. At any rate, we are aiming to have improvements in this area for the next release.
Go to Top of Page

barryl72
Junior Member

15 Posts

Posted - Jun 03 2014 :  03:09:47 AM  Show Profile  Reply with Quote
Great, thanks.
Go to Top of Page

sean
Whole Tomato Software

USA
2641 Posts

Posted - Jun 26 2014 :  01:49:31 AM  Show Profile  Reply with Quote
case=79296 is fixed in build 2042.
Go to Top of Page

barryl72
Junior Member

15 Posts

Posted - Jun 30 2014 :  01:00:09 AM  Show Profile  Reply with Quote
I've just download build 2042 and it works fine. Thanks for this.
Go to Top of Page

sean
Whole Tomato Software

USA
2641 Posts

Posted - Jul 01 2014 :  12:08:39 AM  Show Profile  Reply with Quote
Thanks for the confirmation.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000