Behavior of [projectname].resharper.user in an ASP.NET project under souce control

I've recently started working with a Web App which is under source control.
Problem is, with the new web app format in .NET 2.0, ALL files in the folder
are treated as part of the project. So, it always shows the
*.resharper.user file as a "pending checkin." Or, if I perform a Get Latest
operation, it tries to delete the file since it does not exist in
SourceSafe.
If I go ahead and let it check the file in to make VS happy, then ReSharper
gets mad (file is read-only).

Is there anything I can do about this?

--
Adam Clauss



5 comments
Comment actions Permalink


"Adam Clauss" <cabadam@no@spam.com> wrote in message
news:dvrlo3$6fo$1@is.intellij.net...

Is there anything I can do about this?


I see three alternatives :
- use the 'new' web project template that returns to the previous way of
using web projects (as in 2003, also known as 'the correct one'). I don't
know if it's been officially released yet though.
- use Subversion and TortoiseSVN, which allows you to ignore any file you
don't want to commit (and is basically infinitely better than SourceSafe,
the only drawback being the lack of integration with the IDE, at least until
JetBrains takes care of it :)
- don't use the web project template at all. You can simply use the Class
Library template, set the output to /bin instead of /bin/Debug|Release,
manually create the virtual directory in IIS and simplify your life a whole
lot. The only drawback being that the designer is not avaiable, which is a
big advantage IMO :)


In any case, get away from the 2005 version of web projects. It's probably
the worst thing in VS2005.

Regards,

Lionel


0
Comment actions Permalink

"Lionel Guilhou" <lionel.guilhou@free.fr> wrote in message
news:dvrsk0$hma$1@is.intellij.net...

- use the 'new' web project template that returns to the previous way of
using web projects (as in 2003, also known as 'the correct one'). I don't
know if it's been officially released yet though.


They're going back to the old way? I just about drove myself nuts getting
things working under the new version... (this project was a converted 1.1 to
2.0 project). Grrr... I'll have to poke around and see what I can find out
about that.

- use Subversion and TortoiseSVN, which allows you to ignore any file you
don't want to commit (and is basically infinitely better than SourceSafe,
the only drawback being the lack of integration with the IDE, at least
until
JetBrains takes care of it :)


Yeah, I do not think that is much of an option for us. We globally use
SourceSafe, which is nice with the integration and keeps everyone on the
same system.

- don't use the web project template at all. You can simply use the Class
Library template, set the output to /bin instead of /bin/Debug|Release,
manually create the virtual directory in IIS and simplify your life a
whole
lot. The only drawback being that the designer is not avaiable, which is a
big advantage IMO :)


The designer is definately a big advantage, and if they are switching back
to the old form of the template, that might be the best way to go about it.
Just gotta figure out when that is going to happen.

>

In any case, get away from the 2005 version of web projects. It's probably
the worst thing in VS2005.


Agreed! I wonder how much work it'll take to go BACK to the old way...


--
Adam Clauss


0
Comment actions Permalink

"Adam Clauss" <cabadam@no@spam.com> wrote in message
news:dvs09o$9di$1@is.intellij.net...

"Lionel Guilhou" <lionel.guilhou@free.fr> wrote in message
news:dvrsk0$hma$1@is.intellij.net...
The designer is definately a big advantage, and if they are switching back
to the old form of the template, that might be the best way to go about

it.

Yup, for a designer-style web project, it's most likely the best choice.
There was a way to use the web designer in a class library project in 2003
so there should be one in 2005 too, but I didn't really try to dig in this
direction.
I tried the 2005 way (converting some 1.1 projects in 2.0, so I feel your
pain :), but seeing the horror of it, and since I was already used to the
class library approach (and never use the designer if I can do anything
about it), I simply ended up converting those web projects in class
libraries.
Simple deletion of the .webinfo file, replacing of 'web' by 'local' in the
.csproj file and voilà, VS2005 does the rest. It only took a few seconds for
each :)

If the web designer is needed and can be brought back in class library
projects for 2005, I'd still recommend this way.

Just gotta figure out when that is going to happen.


A usable version of the template is already available (it's been mentioned
here some time ago), but maybe not the 'final' one. Still, it'll be better
than the current model :)

In any case, get away from the 2005 version of web projects. It's

probably

the worst thing in VS2005.

>

Agreed! I wonder how much work it'll take to go BACK to the old way...


Probably not that much.. All the files are already there, it should only be
a matter of creating a project and copying/including the various files. Sure
you'll probably lose the precompiling functionality, but was it really worth
the pain? (or rather, was it ever worth anything?)

Anyway, good luck with that. I hope you'll find an appropriate solution :)
Too bad it's not something that ReSharper can really help with :)


Regards,

Lionel



0
Comment actions Permalink


"Adam Clauss" <cabadam@no@spam.com> schreef in bericht
news:dvs09o$9di$1@is.intellij.net...
>...
>I'll have to poke around and see what I can find out about that.

http://webproject.scottgu.com/Default.aspx

Visual Studio 2005 Web Application Projects (Beta V2 Preview):
http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/

Note:will be officially supported and released soon. Will be part of VS2005
SP1.


>

Agreed! I wonder how much work it'll take to go BACK to the old way...

>
>

--
Adam Clauss

>

Bad luck indeed. Converting to Web Application projects is way easier.

Tips on going back:
- In all @page directives replace "CodeFile" with "CodeBehind" attributes
- Touch all aspx files and hope that the designer.cs gets updated/created.

Success,
Erwin


0
Comment actions Permalink

"Erwin Derksen" <dachthetniet@onbekend.nl> wrote in message
news:dvsbpd$6hf$1@is.intellij.net...

http://webproject.scottgu.com/Default.aspx

>

Visual Studio 2005 Web Application Projects (Beta V2 Preview):
http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/
Bad luck indeed. Converting to Web Application projects is way easier.

>

Tips on going back:
- In all @page directives replace "CodeFile" with "CodeBehind" attributes
- Touch all aspx files and hope that the designer.cs gets updated/created.



Thanks for the links and suggestions!

--
Adam Clauss


0

Please sign in to leave a comment.