I seem to be missing something today (leaving myself open to many comments I'm sure). :roll:
What is the easiest way to move an AS6 project from one HD location to another. How do I get the solution to sync up with the new location?
I hope someone in Europe stays up late to answer this. :D
meolsen 
I hope someone in Europe stays up late to answer this. :D
You know, this time of year, the night is hardly dim in Trondheim 8)
The solution 'should' be relative, so a simple copy and past 'should' be enough.
I'm not able to test this today, as I don't use Windows unless I have to (surprise).
You don't know how many times I tried that this morning and it didn't work. I was even checking the .atsln and .cproj files to see if the changes ocurred after a clean solution and rebuild. Your comment about not using Windows made me decide to reboot. Guess what, it works fine now. :lol:
I too like an alternative (big surprise). :wink:
Thanks Morten.
meolsen
Your comment about not using Windows made me decide to reboot. Guess what, it works fine now.
I stopped being amazed at all the weird things that may happen in Windows quite some time ago. :P
js 
as I don't use Windows unless I have to
There are quite a few who would like multi-platform!
Jim
Torby 
One tip for the designers of studio 6: Store relative path names, not full path names. Of course, since this is Visual Studio, MS is very fond of full path names.
The only place I find full path names is in the non-ascii ".atsuo" file in the main project folder. Don't know what this file is used for.
There are bunches of guid's in the .atsln file. Probably are related to the ATMEL addins to Visual Studio rather than the file location.
If you don't know my whole story, keep your mouth shut.
If you know my whole story, you're an accomplice. Keep your mouth shut. 
meolsen
There are bunches of guid's in the .atsln file. Probably are related to the ATMEL addins to Visual Studio rather than the file location.
In the solution file, most of the GUIDS are for uniquely identification of settings/packages related to the project (e.g Project Configs etc).
The only place I find full path names is in the non-ascii ".atsuo" file in the main project folder. Don't know what this file is used for.
The .atsuo file contains the solution user options. See http://msdn.microsoft.com/en-us/...(v=vs.100).aspx for a basic overwiev.
One tip for the designers of studio 6: Store relative path names, not full path names. Of course, since this is Visual Studio, MS is very fond of full path names.
...as Studio matures.
meolsen meolsen wrote:...as Studio matures.
Will it mature and morph enough to be on linux or Mac?
GTKNarwhal 
Export the project as a template. Create a new project based on the template and specify the new path while doing so. Delete the original project and template if you so desire.
That depends if you want me to say what I hope or what I believe :P . Anyway, I guess you already know the answer to this one
Torby Wow. Thanks for replying, Morten.
So the solution was the template idea? I've been just creating a new project and copy/pasting the source, but then, you just can't get much source into a Tiny 2313
If you don't know my whole story, keep your mouth shut.
If you know my whole story, you're an accomplice. Keep your mouth shut.
No, the solution I used was the copy/paste method mentioned earlier to move the project. I haven't tried the export project template method yet. I'm sure it works as well.
EDIT: I confirmed that both methods work as advertised. Thank you Morten and GTKNarwhal.
JohanEkdahl 
Yes, Microsoft will buy ARM, Nokia, and Atmel on the 18th of June.
In another feeble attempt of trying to get into phones-pads-n-stuff MS might buy Noika tomorrow. I do not see a company trying to grow, or get into new markets, by buying other companies as a strong strategy. One sign of a empire company starting to fall is that it stops growing "organically, IMO. It's like Spain deciding to buy Greece, if you excuse the bluntness..
ARM knows very well what their core business is (if you excuse the pun..). They will not buy neither Atmel, nor Nokia. And of-course not MS. And they will not be bought - why would they? They are a highly successful business with a very promising future.
We know the history about someone trying to buy Atmel (the old scheme of buying a competing business in the same sector) - didn't work, so I assume that other competitors have noted this and are less likely to try. Neither Microsoft, nor Nokia have any use for Atmel.
I think that cover most of the permutations.
Johan, you take things so seriously sometimes. :)
I was just adding, and alluding, to the rumors flying around about Microsoft's coming announcement on Monday. Hardware is most probably involved. 8)
