Need Help: Unable to open or create Model Diagrams in Visual Studio 2010: Illegal characters in path

Question

About a month ago I created several modeling diagrams, class, activity, component.
Now I am unable to open or create any Modeling diagram. I get the following error:
Cannot load 'G:\Projects\trunk\System\Engineering\Architecture\Modeling\Core Business Objects.classdiagram': Illegal characters in path.
The path is valid!

I also get the following error when trying to create a new diagram
Cannot evaluate the item metadata "%(FullPath)". The item metadata "%(FullPath)" cannot be applied to the path "obj\Debug|Any CPU\Modeling.dll". Illegal characters in path.  C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets

In the last month I've installed NuGet and Resharper.

 

 

Answer 1

Hi Brian,

Sorry you are having problems.  I have not seen this issue before.   Does this happen if you create a new Modeling Project and add a diagram, or is this problem only happening on this Modeling Project?

 

Thanks,
Mark

---

Mark Groves | Program Manager | Visual Studio

Answer 2

Hello Brian,

Are you still having this problem, or can we close this out?

 

Thanks,
Mark

---

Mark Groves | Program Manager | Visual Studio

Answer 3

I have tha same problem. After opening solution I have to Unload and Reload Model project. If I will not do that than every operation on this project (open diagram, add folder or any other item, opening UM Model Explorer, ...) will faild with error "Illegal characters in path".

I am not shure but this problem appear when I have instal Resharper 6.0 EAP (exacly it is 6.0.2135.85).

Answer 4

Hi Konrad,

 

Does the problem go away if you don't uninstall ReSharper, and repair?  I would like to track this down so we can figure out if we need to work with JetBrains.

 

Thanks,

Mark

---

Mark Groves | Program Manager | Visual Studio

Answer 5

I have uinstall ReSharper and try to open solution and work on model project. The problem has gone.

Than I have install the newest version 6.0.2151.53 and the problem comes back. So I am almost sure that the problem is releated to Resharper.

Answer 6

Hi, Konrad!

This issue is fixed in next ReSharper build (=>6.0.2152.845)

-- 
Alexander Zverev
JetBrains, Inc.
http://www.jetbrains.com
"Develop With Pleasure!"

Answer 7

Thanks Alexander

---

Mark Groves | Program Manager | Visual Studio

Answer 8

Thanks, it is working now :)