vs2010

[Meinrad Recheis]

I am welcoming Eoin Coffey to GitSharp. He is going to maintain a vs2010 branch.
Would any of the active committers like to switch to vs2010 in the near future?

Yours,
-- henon

[Emeric Fermas]

>I am welcoming Eoin Coffey to GitSharp. He is going to maintain a vs2010 branch. 

Welcome to the project!

>Would any of the active committers like to switch to vs2010 in the near future?

I'm still going to stick to VS2008 for a while.

Em.

--
For infos about GitSharp visit http://www.eqqon.com/index.php/GitSharp
To join this group visit http://groups.google.com/group/gitsharp

[Eoin Coffey]

On Fri, Jan 22, 2010 at 12:33 PM, Emeric Fermas <emeric...@gmail.com> wrote:
>>I am welcoming Eoin Coffey to GitSharp. He is going to maintain a vs2010
>> branch.

> Welcome to the project!
>>Would any of the active committers like to switch to vs2010 in the near
>> future?
> I'm still going to stick to VS2008 for a while.

Thats understandable. It is still in beta. I wanted to play with the
code last night and beta 1 was all I had installed, since I've been
too lazy to get vs2008 from work again after win 7 upgrade.

I also offered to hammer on this in Linux as well, to make sure we're
properly covering mono.

[Emeric Fermas]

>Thats understandable.  It is still in beta.  I wanted to play with the
>code last night and beta 1 was all I had installed, since I've been
>too lazy to get vs2008 from work again after win 7 upgrade.

In fact, I think I'm myself too lazy to install VS2010 yet ;-)

BTW, Does VS2010 allows to target both .Net 3.5 and .Net 3.5SP1, or is it 3.5 SP1 by default ?

>I also offered to hammer on this in Linux as well, to make sure we're
>properly covering mono.

As our CI server is temporarily down, I would be very glad if you could run the test suite and confirm nothing has been broken on this side.

Em.

[Eoin Coffey]

On Fri, Jan 22, 2010 at 2:02 PM, Emeric Fermas <emeric...@gmail.com> wrote:
>>Thats understandable.  It is still in beta.  I wanted to play with the
>>code last night and beta 1 was all I had installed, since I've been
>>too lazy to get vs2008 from work again after win 7 upgrade.
> In fact, I think I'm myself too lazy to install VS2010 yet ;-)
> BTW, Does VS2010 allows to target both .Net 3.5 and .Net 3.5SP1, or is it
> 3.5 SP1 by default ?

Hmm, I'm not sure. I can check tonight. Is 3.5 what we're targeting?

>>I also offered to hammer on this in Linux as well, to make sure we're
>>properly covering mono.
> As our CI server is temporarily down, I would be very glad if you could run
> the test suite and confirm nothing has been broken on this side.

Sure, probably happen later tonight / tomorrow. Glad to see we have
some sane processes in place :-)

-Eoin

[Emeric Fermas]

>Is 3.5 what we're targeting?

We're trying not to depend on SP1.

>Sure, probably happen later tonight / tomorrow.  Glad to see we have
>some sane processes in place :-)

Thanks a lot! 

Em.

[Eoin Coffey]

On Fri, Jan 22, 2010 at 2:47 PM, Emeric Fermas <emeric...@gmail.com> wrote:
>>Is 3.5 what we're targeting?
> We're trying not to depend on SP1.

Why for? Is mono missing some of those pieces?

[Meinrad Recheis]

On Fri, Jan 22, 2010 at 10:59 PM, Eoin Coffey <eco...@gmail.com> wrote:

On Fri, Jan 22, 2010 at 2:47 PM, Emeric Fermas <emeric...@gmail.com> wrote:
>>Is 3.5 what we're targeting?
> We're trying not to depend on SP1.

Why for?  Is mono missing some of those pieces?

no it's just awkward not being able to compile the source without installing .net SP1. I don't want to scare off potential contributors.
-- henon

[snipped]

[Eoin Coffey]

Fair enough, although my guess is that anyone interested in deving on
this is already going to have an up to date development environment,
*shrug*.

-Eoin

> -- henon
>
> [snipped]

[James Gregory]

I find that an odd requirement, I'm fairly certain that the vast majority of people who have .Net installed also have SP1.

http://www.hanselman.com/blog/HowManyPCsInTheWorldHaveTheNETFrameworkInstalled.aspx

[Meinrad Recheis]

On Fri, Jan 22, 2010 at 11:04 PM, Eoin Coffey <eco...@gmail.com> wrote:

On Fri, Jan 22, 2010 at 3:01 PM, Meinrad Recheis
<meinrad...@gmail.com> wrote:
>
> On Fri, Jan 22, 2010 at 10:59 PM, Eoin Coffey <eco...@gmail.com> wrote:
>>
>> On Fri, Jan 22, 2010 at 2:47 PM, Emeric Fermas <emeric...@gmail.com>
>> wrote:
>> >>Is 3.5 what we're targeting?
>> > We're trying not to depend on SP1.
>>
>> Why for?  Is mono missing some of those pieces?
>
> no it's just awkward not being able to compile the source without installing
> .net SP1. I don't want to scare off potential contributors.

Fair enough, although my guess is that anyone interested in deving on
this is already going to have an up to date development environment,
*shrug*.

-Eoin

I wish you were right ... ;)
Well, if it were really holding us back (which is really not the case at the moment) we can still force those to upgrade to SP1 or leave. Until then why bother?
On the other hand, not upgrading to .net 4.0 when it's time might really hold us back.

cheers,
-- henon

[...]

[Eoin Coffey]

On Fri, Jan 22, 2010 at 3:25 PM, Meinrad Recheis

<meinrad...@gmail.com> wrote:
> On Fri, Jan 22, 2010 at 11:04 PM, Eoin Coffey <eco...@gmail.com> wrote:
>>
>> On Fri, Jan 22, 2010 at 3:01 PM, Meinrad Recheis
>> <meinrad...@gmail.com> wrote:
>> >
>> > On Fri, Jan 22, 2010 at 10:59 PM, Eoin Coffey <eco...@gmail.com> wrote:
>> >>
>> >> On Fri, Jan 22, 2010 at 2:47 PM, Emeric Fermas
>> >> <emeric...@gmail.com>
>> >> wrote:
>> >> >>Is 3.5 what we're targeting?
>> >> > We're trying not to depend on SP1.
>> >>
>> >> Why for?  Is mono missing some of those pieces?
>> >
>> > no it's just awkward not being able to compile the source without
>> > installing
>> > .net SP1. I don't want to scare off potential contributors.
>>
>> Fair enough, although my guess is that anyone interested in deving on
>> this is already going to have an up to date development environment,
>> *shrug*.
>>
>> -Eoin
>
> I wish you were right ... ;)
> Well, if it were really holding us back (which is really not the case at the
> moment) we can still force those to upgrade to SP1 or leave. Until then why
> bother?
> On the other hand, not upgrading to .net 4.0 when it's time might really
> hold us back.

Oh no, I'm not passionate on the subject, just curious :-)

If it works for us and I still get my var keyword, linq extensions,
and lambdas I'm a happy man :-)

-Eoin

>
> cheers,
> -- henon
>
> [...]

[Emeric Fermas]

Maybe could we just have a 2010 version of the .sln and the .csproj files sitting next to the 2008 version.

In order to avoid keeping them in sync when adding files, maybe could we produce a quick console app taking charge of the automatic conversion. If I recall correctly such solutions were already existing dealing with 2005 and 2008 projects.


Em.

[James Gregory]

+1 to that idea.

[Eoin Coffey]

On Sat, Jan 23, 2010 at 9:09 AM, James Gregory <jagreg...@gmail.com> wrote:
> +1 to that idea.
>
> On Sat, Jan 23, 2010 at 3:35 PM, Emeric Fermas <emeric...@gmail.com>
> wrote:
>>
>> Maybe could we just have a 2010 version of the .sln and the .csproj files
>> sitting next to the 2008 version.
>> In order to avoid keeping them in sync when adding files, maybe could we
>> produce a quick console app taking charge of the automatic conversion. If I
>> recall correctly such solutions were already existing dealing with 2005 and
>> 2008 projects.

A console app, or just a GitSharp-vs2010.sln file :-P

-Eoin

[Meinrad Recheis]

On Sat, Jan 23, 2010 at 5:43 PM, Eoin Coffey <eco...@gmail.com> wrote:

On Sat, Jan 23, 2010 at 9:09 AM, James Gregory <jagregory.com@gmail.com> wrote:
> +1 to that idea.
>
> On Sat, Jan 23, 2010 at 3:35 PM, Emeric Fermas <emeric...@gmail.com>
> wrote:
>>
>> Maybe could we just have a 2010 version of the .sln and the .csproj files
>> sitting next to the 2008 version.
>> In order to avoid keeping them in sync when adding files, maybe could we
>> produce a quick console app taking charge of the automatic conversion. If I
>> recall correctly such solutions were already existing dealing with 2005 and
>> 2008 projects.

A console app, or just a GitSharp-vs2010.sln file :-P

if the project file format hasn't changed, and it seems to be so, the latter would be a nice solution.
-- henon

[...]

[Eoin Coffey]

On Sat, Jan 23, 2010 at 9:46 AM, Meinrad Recheis
<meinrad...@gmail.com> wrote:
> On Sat, Jan 23, 2010 at 5:43 PM, Eoin Coffey <eco...@gmail.com> wrote:
>>

>> On Sat, Jan 23, 2010 at 9:09 AM, James Gregory <jagreg...@gmail.com>

>> wrote:
>> > +1 to that idea.
>> >
>> > On Sat, Jan 23, 2010 at 3:35 PM, Emeric Fermas <emeric...@gmail.com>
>> > wrote:
>> >>
>> >> Maybe could we just have a 2010 version of the .sln and the .csproj
>> >> files
>> >> sitting next to the 2008 version.
>> >> In order to avoid keeping them in sync when adding files, maybe could
>> >> we
>> >> produce a quick console app taking charge of the automatic conversion.
>> >> If I
>> >> recall correctly such solutions were already existing dealing with 2005
>> >> and
>> >> 2008 projects.
>>
>> A console app, or just a GitSharp-vs2010.sln file :-P
>
> if the project file format hasn't changed, and it seems to be so, the latter
> would be a nice solution.
> -- henon
>

Actually it does look like the vs2010 upgrade touched the .csproj
files, so something like Emeric suggested would be better.

Also: does anyone else idle in #gitsharp on freenode? The room is
looking a bit sparse at the moment :-P

-Eoin

[Emeric Fermas]

If we want to ensure that the two solution will be kept in sync, I think that we need to somehow automate the project conversion back and forth between 2008 and 2010 and ease the developer job.

How about something like :

-Two apps ConvertSlnAndCsprojFrom2010To2008.exe and ConvertSlnAndCsprojFrom2008To2010.exe

-Those apps would be checked in at the root of the GitSharp project.

-Each time one would alter the .sln/.csproj files, depending on the used IDE, the appropriate app would have to be launched. 

-The apps would work down the folder hierarchy from their current position in search of files bearing expected extensions to work with.

-...Magic happens...

Feel free to counter propose.

Em.

On Sat, Jan 23, 2010 at 6:06 PM, Eoin Coffey <eco...@gmail.com> wrote:

On Sat, Jan 23, 2010 at 9:46 AM, Meinrad Recheis
<meinrad...@gmail.com> wrote:
> On Sat, Jan 23, 2010 at 5:43 PM, Eoin Coffey <eco...@gmail.com> wrote:
>>

>> On Sat, Jan 23, 2010 at 9:09 AM, James Gregory <jagregory.com@gmail.com>

[Eoin Coffey]

On Sat, Jan 23, 2010 at 10:44 AM, Emeric Fermas <emeric...@gmail.com> wrote:
> If we want to ensure that the two solution will be kept in sync, I think
> that we need to somehow automate the project conversion back and forth
> between 2008 and 2010 and ease the developer job.
> How about something like :
> -Two apps ConvertSlnAndCsprojFrom2010To2008.exe
> and ConvertSlnAndCsprojFrom2008To2010.exe
> -Those apps would be checked in at the root of the GitSharp project.
> -Each time one would alter the .sln/.csproj files, depending on the used
> IDE, the appropriate app would have to be launched.
> -The apps would work down the folder hierarchy from their current position
> in search of files bearing expected extensions to work with.
> -...Magic happens...
> Feel free to counter propose.
>

Hmm yeah something like that seems feasible. Assuming we can figure
out the magic happens part :-P. For the .csproj files, at a glance,
it seems to just be changing the build tools version from 3.5 to 4.0

-Eoin

> Em.
>
>
> On Sat, Jan 23, 2010 at 6:06 PM, Eoin Coffey <eco...@gmail.com> wrote:
>>
>> On Sat, Jan 23, 2010 at 9:46 AM, Meinrad Recheis
>> <meinrad...@gmail.com> wrote:
>> > On Sat, Jan 23, 2010 at 5:43 PM, Eoin Coffey <eco...@gmail.com> wrote:
>> >>
>> >> On Sat, Jan 23, 2010 at 9:09 AM, James Gregory

>> >> <jagreg...@gmail.com>

[Emeric Fermas]

I think that most of the magic has already been figured out in 2005<->2008 project converters.

Moreover, we need something something very light, targeted at GitSharp.


Em.

>> >> <jagregory.com@gmail.com>

[Meinrad Recheis]

another way to achieve the same goal would be to continually rebase vs2010 on master and cherry pick commits back. but of course I can't judge how much work that is compared to hacking together a converter.

-- henon

[Emeric Fermas]

I think that finding out some open source code shouldn't be _that_ complex :-)

http://www.google.fr/search?hl=en&q=convert+2008+sln+2005


Em.

[Emeric Fermas]

A new kid on the block to deal with 2008 <-> 2010 automatic project conversions.

http://stevedunns.blogspot.com/2010/02/tool-to-switch-project-files-between.html

Em.

>>>> >> >> <jagreg...@gmail.com>

[Meinrad Recheis]

so you are back and well! good ;)

>>>> >> >> <jagregory.com@gmail.com>

To unsubscribe, reply using "remove me" as the subject.