Re: Visual Studio Solution

I'd be interested since I do like the IDE environment myself too.
However, I wouldn't suggest it be checked in since it'd likely just
rot. What you could do is create a Makefile project that just uses the
existing Makefile system perhaps. That way it wouldn't rot over time.

Eventually, I see things moving from nmake to msbuild personally, and
current Visual Studio solutions and projects are just msbuild files in
disguise. That'd be a nice route too.

Brant Gurganus
http://gurganus.name/brant



On Mon, Aug 24, 2009 at 7:27 PM, Mickey Lane<[email protected]> wrote:
> I would like to know if there is any interest in the OpenAFS for Windows
> community for a Visual Studio Solution for the Windows client.
>
>
>
> I have one (VS 2008) that contains projects for most of the libraries, DLLs
> and executables. It'll need some work before it's usable by anyone other
> than myself. If there's interest, I don't mind doing that work and making it
> available, time permitting.
>
>
>
> The solution I implemented lives in a peer directory of the src, doc, obj
> and dest directories. The files it builds wind up under that peer directory,
> not in the existing obj and dest directories. The peer output directory
> structure mimics the existing obj and dest output structure. The solution
> does not require any modifications the existing source code, build files,
> etc in any way.
>
>
>
> My reason for doing this is that after many years, I am most comfortable
> searching, navigating and editing within the Visual Studio environment. I
> use it all the time. It was easier for me to do this than it was to deal
> with a different set of tools.
>
>
>
> While the solution has built components that have successfully executed in
> conjunction with the files from the current install package and the run-time
> debugging things work, I do not suggest that the solution be considered a
> replacement for the current build process. It could be some day but it'd
> take a awful lot of testing and proving before I'd trust it.
>
>
>
> Comments?
>
>
>
> Mickey.
>
>