Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
ability to save VS projects as you go?
Options
Previous Topic Next Topic
DamonOverboe
#1 Posted : Monday, February 25, 2013 4:54:46 PM(UTC)
Rank: Member

Groups: Registered
Joined: 7/20/2012(UTC)
Posts: 10
Location: Springfield, MO, USA

Thanks: 4 times
Was thanked: 2 time(s) in 2 post(s)
I'm using VS 2012, NCrunch, and xUnit and writing TDD, with svn as the repo.

It's probably a matter of I just have to get this worked into my workflow, train myself.

But what I'm seeing is as I'm coding, I'm adding files as needed, and running my tests. I have `C+t` and `CS+t` bound to NCrunch: Run Test, and NCrunch: Debug Test in new processes.

So what's happening is I'm no longer firing off a full build, even before I commit; maybe I've gotten too lazy or spoiled :-D The result is that my project changes where I'm adding and/or removing files are not saved.


This causes two potential problems:

  1. I'm not committing up the changes I should be (I usually catch that)
  2. When I update before committing, sometimes my changes get clobbered because someone else committed project changes and I haven't saved mine locally.


Again I know I can "fix" my habits and workflow, but I'm curious if there's a setting in NCrunch or VS that would help me out here?
Back to top
WWW
Remco
#2 Posted : Monday, February 25, 2013 10:13:02 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,123

Thanks: 957 times
Was thanked: 1286 time(s) in 1193 post(s)
Hi, thanks for posting!

Many people, including myself, also occasionally suffer from this. It's a problem that can be a bit entertaining in some ways - that you're able to do a considerable amount of reliable work on your solution without ever building or even saving it, and feel safe enough to dump it straight into a source control system without feeling the need for extra checking.

Although the solution to this can seem quite obvious (i.e. auto-save of the project), in implementation it is actually very difficult. Automatically saving a project file on its own after changes would only solve part of the problem, as any changed source files would need to be automatically saved to disk too. At present I'm not yet aware of a reliable way to handle the continuous saving of source files that won't interfere with Visual Studio at some level - for example, every time you save a file in VB.NET, the file is automatically reformatted by the IDE.

The correct approach to solving this problem may become more obvious in future as NCrunch matures into new feature areas.

Cheers,

Remco
Back to top
DamonOverboe
#3 Posted : Monday, February 25, 2013 11:18:01 PM(UTC)
Rank: Member

Groups: Registered
Joined: 7/20/2012(UTC)
Posts: 10
Location: Springfield, MO, USA

Thanks: 4 times
Was thanked: 2 time(s) in 2 post(s)
Well I'm glad to hear I'm not the only one suffering from it. :-D

Yeah, before NCrunch if someone told me they never fire off a full build before committing, I'd probably just give them a nice blank stare.

No worries that it hasn't been implemented, I just wanted to see if there was a workaround. If I mess up too many more times, I'll learn to save all before updating. I'm really spoiled by it building in the background, so I don't see myself going back to build-all, but you never know. Maybe it'll be a good excuse to get out of the chair for a few.
Back to top
WWW
1 user thanked DamonOverboe for this useful post.
Remco on 2/26/2013(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.033 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download