| Author |
 Topic  |
|
|
Ephemeral
New Member
USA
8 Posts |
 Posted - Nov 15 2013 : 11:01:54 AM
|
When I try to add any files to a solution I get this error popup, I narrowed it down to VA:X because it went away when I disabled the VAX extension in VS2013.
The file is created on the disk, it just doesn't get put into the solution and that error is thrown, this also happens when I try and remove a file in the solution that doesn't exist anyways. |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 15 2013 : 4:23:42 PM
|
Can you please post a screenshot of this error dialog?
(You can easily attach a picture after you click on the "Reply to Topic" link.)
What Visual Assist version are you using? |
 |
|
|
Ephemeral
New Member
USA
8 Posts |
Posted - Nov 16 2013 : 2:21:28 PM
|
2001
After adding source2.cpp to Entities filter, it also happens if I try and add it to the project at broad.
|
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 18 2013 : 3:53:28 PM
|
Thank you for sharing the screenshot.
This is unexpected.
- Are you using a network or virtual drive to create the files on?
- Are you using any other Visual Studio extensions?
- Which Windows version are you using?
- The project seems to be rather small. Is it a test project? Would it be possible to send in this project so I could try reproduce the problem here using your project? It would be kept private.
Just zip it up and you can send it via the following form:
http://www.wholetomato.com/support/contact.asp
Please paste the URL of this topic into the description field so we can match it up. |
Edited by - accord on Nov 18 2013 3:54:17 PM |
|
|
|
Ephemeral
New Member
USA
8 Posts |
Posted - Nov 19 2013 : 1:32:26 PM
|
No, and to clarify the files ARE made on the disk, and they show next time you open the IDE+Project, but not off the bat, which isn't right.
Yes, But I tried disabling the rest of them and it still happened even with just VAX running.
8.1
No it wasn't a test project but it was a project I wanted to kick off with the new C++11 features in VS2013, And it happens to all other C++ projects I've tried, including a rather large game I work on that worked fine in VAX with VS2012.
|
Edited by - Ephemeral on Nov 19 2013 4:19:56 PM |
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 20 2013 : 7:18:58 PM
|
Thank you for the clarification. I wasn't able to reproduce the problem here, using Visual Assist 2007/2001, Visual Studio 2013 and Windows 8.1.
Can you please try installing Visual Assist build 2007 just to see if it makes any difference?
http://www.wholetomato.com/downloads/default.asp
We've fixed a few VS2013 related issues in the latest build.
If you're still seeing the problem, can you please describe the exact steps you're adding the new file? So I will see if it's triggered via the Context menu/File menu, mouse/keyboard, new file/adding existing one, etc. I tried combinations, but nothing produced the error dialog for me.
Also, can you please export and send in your Visual Assist and Visual Studio settings, so I will import them here and try reproduce the problem using your settings.
1. VA Options -> Performance -> Export Settings
2. IDE tools menu -> Import and Export Settings -> Export selected environment settings
You can send in the files using the following form:
http://www.wholetomato.com/support/contact.asp
Please paste the URL of this topic to the description field so we can match it up. |
|
|
|
Ephemeral
New Member
USA
8 Posts |
Posted - Nov 21 2013 : 06:17:01 AM
|
right click -> add new file.. Try on source or header, same thing.
right click -> new class -> makes the src/header automatically, the error doesn't show; BUT the files still don't appear.
right click -> add existing -> adds the files that I made in either of the earlier two steps fine..
Already tried upgrading to 2007 build, same issue.
And sent.
Is there any sort of log-mode for Visual Assist, or a debug build thing?
|
Edited by - Ephemeral on Nov 21 2013 06:35:47 AM |
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 21 2013 : 5:23:38 PM
|
We got the files, thank you. Unfortunately I wasn't able to reproduce your problem.
I've asked a developer to take a look at your log files. |
|
|
|
Ephemeral
New Member
USA
8 Posts |
Posted - Nov 21 2013 : 11:46:03 PM
|
| Thanks, hopefully this can get resolved, it feels like I'm using notepad without VAX :( |
|
|
|
Ephemeral
New Member
USA
8 Posts |
Posted - Nov 24 2013 : 6:27:06 PM
|
Has there been any headway in this?
|
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 25 2013 : 4:48:51 PM
|
| No, not yet, unfortunately. |
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 27 2013 : 4:05:59 PM
|
| The discussion is being continued via email. |
|
|
|
Ephemeral
New Member
USA
8 Posts |
Posted - Dec 02 2013 : 04:37:19 AM
|
| Haven't received any email as of yet. |
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Dec 02 2013 : 3:51:10 PM
|
*oops*
This is strange. Someone, probably you, have sent us 2 emails from a gmail address. The second was for the forgotten logs (valog.rar). The first reply was from Mark on 11/26/2013 and you replied "I already tried every permutation of disabling/enabling addons, and it only ever went away when VAX was disabled. And resharper is 8.0.2"
Was it you?
Two more emails were sent to you Today by Mark. Did you get them? |
|
|
|
Ephemeral
New Member
USA
8 Posts |
Posted - Dec 05 2013 : 12:50:19 AM
|
Yes.
I do apologize I may have gotten my stuff on my thunderbird mixed up and used wrong email. |
Edited by - Ephemeral on Dec 05 2013 12:51:07 AM |
|
|
|
Vladik
New Member
2 Posts |
Posted - Dec 23 2013 : 2:32:47 PM
|
I've the same error with the newest VAX-2023 try version too.
In my case, this error message VS2013 shows on any Project property change.
I've enabled vax logging, but the only log is startup.log
like this:
InitInst::165 12/23/2013 23:46:31 0x5ac
Init2::172 12/23/2013 23:46:36 0x5ac
TI: 0-7:213 12/23/2013 23:46:36 0x5ac
EDL: 7, 0, :230 12/23/2013 23:46:36 0x5ac
Init2ex::349 12/23/2013 23:46:38 0x5ac
So, is there any solution for this problem?
|
|
|
|
Vladik
New Member
2 Posts |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Dec 24 2013 : 12:12:47 PM
|
The original problem seemed to be a Visual Studio bug, but the fact it happens on every "Project property change" is odd and it might be a different problem.
I replied via email.
Sorry for the inconveniences. |
Edited by - accord on Dec 24 2013 12:13:21 PM |
|
|
|
beru
Starting Member
1 Posts |
Posted - Jul 24 2015 : 09:35:47 AM
|
| This is also happening with build 2068 on final release of VS2015 -> bad path error when adding files to project and 'One or more error occured' when changing project properties. These errors go away when VA is disabled. |
|
|
|
deadc0de
New Member
USA
2 Posts |
Posted - Aug 14 2015 : 05:09:47 AM
|
| I am seeing this problem with build 2068 on VS Community 2013. It works fine with VS Professional 2012. Uninstalling or disabling the extension makes the problem go away. |
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Aug 21 2015 : 12:42:56 AM
|
We added a registry item in build 2068 to help with these project editing "One or more errors occurred" messages. We found that (at least for one user) the Visual C++ Durango platform configuration was somehow borked. case=89177
The registry value prevents VA from interacting with all VC++ platform configurations except for those listed (it is a whitelist); it is not created by default.
The value is a string named "PlatformWhitelist" located in the HKCU\\Software\\Whole Tomato\\Visual Assist X\\[VaNet14|VaNet12|VaNetXXX]\
Create it and set the value to Win32 for basic VA functionality.
Alternatively, capture a log of solution load and send it in to support referencing this thread as instructed by accord in the previous post.
|
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Aug 29 2015 : 11:52:37 PM
|
This error can also occur after installation of Windows Driver Kit 10. case=91655
case=91655 is fixed in build 2074
|
|
|
|
deadc0de
New Member
USA
2 Posts |
Posted - Sep 05 2015 : 02:16:06 AM
|
Hi Sean. Thanks for your reply. I sent you guys a couple logs generated when I get this error.
I downloaded build 2068 and added the PlatformWhitelist value with "Win32;x64" and I was able to add files once again. I do have the Durango platform available on the system I am having issues on. However, I also have a similar setup on another workstation (Durango XDK, VS2012/2013) but the order the products were installed may have been different. |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Sep 05 2015 : 12:34:06 PM
|
| Thanks for the information. We have not identified the exact circumstances of the Durango related issue, however the next release (after 2074) should be sufficient without requiring tweaking of the PlatformWhitelist reg value. |
|
|
| |
Topic |
|
One or more errors occurred.
