Unhelpful error message

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If the .cppproj file or the .xml file are write protected, I get the following error.  Yes, I know what it means now, but it took a while.

 

I'm using 7.0.1417.

 

I suppose I might be the only one that gets write protected files.  It happens when I archive them to Source Safe.

 

F:\Archiveable\AVR_butterfly\Xmega\Test\Set_and_export_clock\Set_and_export_clock.cppproj : error  : Value cannot be null.
Parameter name: url

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

steve17 wrote:
I suppose I might be the only one that gets write protected files

No - you aren't.

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Sorry but WHAT is producing this error message? Clearly not the C compiler itself - it does not write to source file and is happy to compile read-only ones.

 

Are you saying this is Studio 7 when you edit (or rather attempt to save) the file, or something else?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It seems to be a general Visual Studio thing - googling the message gives lots of VS hits ...

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

steve17 wrote:
I suppose I might be the only one that gets write protected files.  It happens when I archive them to Source Safe.

 

I'll risk the snide teen-style comment: Locking version control systems are sooo last century.

 

The philosophy with those are that when you want to have files write-able you check them out. IIRC from my SourceSafe days, if you wanted to save a revision of files, and then immediately continue working on them the procedure was a check-in immediately followed by a check-out. I know, if you miss this you will get that really bad error message.

 

If you're the decision-maker re the version control system you use then perhaps take a look at something merely 15 years old (Subversion) or merely 10 years old (Git). Both of those are non-locking by default.

 

A locking system avoids potential conflicts by ... locking. Problem is that a lot of locks will be made without actually needing to, and in multi-developer teams its a lot of "gravel in the gears".

 

A non-locking (optimistic) system does not prevent conflicts but detects them when they occur (and not when they don't occur!), and provides tools to solve the conflict at that time. This scheme has been the future of version control systems for at least 15 years now, and I know of no version control system introduced over the last 15 years that was/is locking by default.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

but version control isn't the only reason one might encounter read-only files ...

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No, I agree. And also on the shitty'ness of the error message.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:

I'll risk the snide teen-style comment: Locking version control systems are sooo last century.

Snide comments are always welcome.  smiley

 

I don't know why the files get locked, but your suggestion makes sense.  I do all my editing with my editor and when I try to save a read-only file, it's just one hover and one click of the mouse to unlock it.

 

SourceSafe has some very handy command-line commands that my editor uses. 

 

My archiver is less than 20 years old, and I can prove it.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:

Sorry but WHAT is producing this error message?

I suppose when I change the project like adding or removing a file, Studio has a hissy fit.  Usually it's the .proj file but sometimes it's the .xml file that gets Studio all bent out of shape.

 

This calamity also happens when I upgrade Studio, and then Studio tries and fails to upgrade a project.  Upgrading to Studio 7 is the first time I can remember having this problem. 

Last Edited: Tue. Oct 24, 2017 - 11:47 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This scheme has been the future of version control systems for at least 15 years now

Certainly ahead of its time! smiley

When in the dark remember-the future looks brighter than ever.   I look forward to being able to predict the future!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Steve, from studio4 to studio 6 will indeed not have given the problem as then the whole new cproj extension was created. so instead of upgrading an existing file a complete new file has been made.