1

Resolved

Settings error when creating new project

description

Hello!
 
First off, great job! Keep up the good work.
 
I just downloaded 2.1.3. I had no previous version installed, and I'm running VS2008 SP1.
 
I jumped at the gun and created a new SPVisualDev project (no solution created). The project gets succesfully created, but when I'm redirected to the settings part of the process an exception is thrown. The same exception is also thrown when I right click and chose Artifact config. I've attached the error message as an image in this post.
 
However, after I save the project and open it again the exception is not thrown anymore and I can change the Artifact config.
 
Hope this is of help.
 
Best regards!

file attachments

comments

tore7506 wrote Dec 11, 2009 at 10:53 AM

Ok, i've looked in the source code and found what the problem could be, but I would apriciate if you could describe little more what OS you are running and other system parameters that would help me reproduce the problem. As far as I can see it probably has to do with the solution settings file. For some reason it cant find the path to the solution and tries to read a settings file that doesnt exist.

Here are some checkpoints:
Could it be that the solution is on a network drive?
Can you see the solution node in the solution explorer in VS?
What path does the solution point to when it is marked in solution explorer (view in property window, press F4)?

The method indicated in the error report assumes it has a valid solution file when it is being called which should be the normal behavior, but it would be great if we could try locate the underlying problem so proper fixes to the code can be made.

Thank you for reporting the problem by the way!

Regards,
Tony

pianif wrote Dec 11, 2009 at 11:52 AM

  • I'm running Windows 2003.
  • I'm running from local disk (no network drive).
  • There is no solution node in Visual Studio. No solution is created when I create a new SPVisualDev project.
  • As I said, once I've saved the project and re-open the project, the exception is not being thrown anymore. However, I still haven't got a solution node in Visual Studio.
I've posted an image which shows what the project looks like. It's just created and un-saved.

wrote Dec 11, 2009 at 11:52 AM

tore7506 wrote Dec 11, 2009 at 3:00 PM

Fixed as explained earlier in my comments.

Regards,
Tony

wrote Feb 14, 2013 at 12:23 AM

wrote May 16, 2013 at 5:08 AM

wrote May 16, 2013 at 5:08 AM

wrote Jun 14, 2013 at 7:51 AM