Hi Brian,

Thanks for the clear report. Some interesting points here.

I can tell you that the Release and Debug folders are not created by VM but are a part of how Atmel Studio works. It creates these folder based upon the projects output folder properties.

Visual micro actually builds to a different location which you can see if you switch on tools>options>visual micro> compiler>show build folder.

In the last release vm does copy the final build files to the projects current output config folder (release/debug). This was designed as a step towards better integration arduino>atmel but hopefully vm does not bother to report an error during the copy because it is not critical.

The intellisense in atmel studio is provided by a free plugin that atmel installs as standard called VisualAssistX. It is visualassistx that is having this problem.

Visual Micro simply uses a standard atmel project and I have no idea why folders would be created as readonly. Where are you creating your projects on your pc, maybe permissions is playing a part in this?

ps: 1) As concerns visual micro in atmel studio 6.1, project properties will only be available in the August 2013 release. 2) Problems after install are usual resolved by running the install and clicking Remove then running again and clicking Install.

Yes- I know that Arduino, and probably VM, use a temp folder in the users/app data/local settings ...... folder, usually hidden.That is a pain to access normally, which is why I like the fact that VM (also) put these folders in the users project folder.
I am creating my project in the default Arduino location i.e.
My Documents/arduino.
While Arduino doesn't put any of its temporary/output files into this project folder, the only files you need to move from one machine to another are the .ino file, and whatever includes/libraries you use, and none of these are read-only, so moving them from computer to computer is no problem.  I am pretty sure I have also accessed the arduino folder existing on my NAS(used for backup normally )  from both computers, with no issues.(not concurrently of course)
Thanks

Hi Tim
In response to your request for a .h filename:
I was sure I saw some error messages about unable to access files in debug and release folders. However, when I do it again, I see that the path was the Visual Micro folder, and the file was vsarduino.h. 
  This shows up several times- I sent you a screen capture.
  Unless my situation is unique, I would still maintain that one should be able to copy a complete project folder from computer to computer, and not run into this error message.

Try excluding .h files from folders below the sketchbook folder from the virus checker?

Hi Brian,

Thanks for the sentiment and the reminder about the final payment page. 

The donate button was never used (one or twice) so I removed it from the site, that way I could pretend that lots of people would donate if given the opportunity. It worked better for my motivation that way   

Seriously though, I appreciate the thought. I think charging for the debugger was the first step towards justifying the time but also towards getting some pro help. 

Initially this has resulted in the new documentation which has been written for vm by Heinz Kessler. I hope continued sales allow Heinz to invest more of his time in Visual Micro because he also has the dev skills required to take the product to the next level.

Over the coming months the current "paid for" debugger+ version of Visual Micro will be renamed to "Gold" and cheaper less featured versions will be released. Hopefully this will then ensure enough revenue to support the huge changes heading our way from the embedded world.

Look forward to hearing the results of your tests

Hi Tim: Tried out some things and believe I have the answer. Its a bit involved so bear with me
  When I told you that the vsarduino.h file was showing as read-only, that was as shown on the XP computer that the project originated on. I did not dream this, but no longer see the read-only tag when I look now- whether I have the project open or not in Studio. I'd say it was a "senior's moment" (I'm in my 60s) but I'm really sure of what I saw before.
However, the same error report still occurs when I try to load it on the 2nd (win7) computer. I had previously not looked at the file attributes on this computer- only on the originating XP.
So, now I see that the .vsarduino.h (full name is .powersupply2.vsarduino.h)  is showing as HIDDEN but not Read-only. I can see the file in File explorer because I must have set it up to view hidden files in the arduino folder at some point in the past, I guess.
  Tracking things down, I found that when I copy the folder to my WD Worldbook Network drive, this file is now hidden- i.e. it isn't visible to me. It's still there of course, and when I then copy the folder to my Win 7 computer, I can now see it, for the reason I mentioned above. If I now toggle the hidden flag off, the project now loads fine in Studio/VM.
  Now it makes sense to me. I know from when I use Linux, the full stop at the start of a filename makes it a hidden file. The WD Worldbook NAS runs under Linux, so it is making the change on the file, even though it really should leave Windows files alone in this respect. 
  If it is not clear, I was copying the folder from XP -> WD NAS  -> Win 7, and the WD NAS in the mddle was causing the problem.
  But, I suspect that this may crop up for anyone using a network drive which is Linux-based, so you may see this again.
  I really liked the docs done by Heinz that you gave me the link to. But, I deleted a lot of the VM forum emails, as they are just notifications, and I can't seem to find that link now.
  Also, tonight I found the link to the VM Beta, which is what I should be using on the Win 7 computer as I had to put Studio 6.2 on it to get things to work. However, I couldn't find the beta link at that time, so I  used the normal version. It is a bit obscure- if you just click the purple button marked download, which is right above the VM for 6.x wording, you don't get the BETA of course, but since it says 6.x, I didn't really worry about it.
If you use the downloads TAB, then you can see both versions, so I''ll reload my Win 7/studio6.2 computer with the beta VM. 
I'll be licensing that machine next.
regards

I uninstalled VM, and then went to download the Beta version. I'm confused- I thought I had been running on the standard release (1404.01)  (which I got by clicking the purple download button) , but when I click on the beta channel, I still see 1404.01. So, I just downloaded this (probably the same file I had before) and re-installed.
Maybe I'm missing something.

Figured that