James Park (pencil_ethics) wrote:
The thing is, I don't think I should ever get commit access since I only
know so much C/C++ (I _knew_ I should have made the point earlier),

:) I read that ...

but it didn't stop me from making a good fist of it ;-) As a result, while I
can get the whole thing to work, I don't have any good ideas on how to
completely eliminate that funny C# class. Although I got the jagged
array syntax correct it seems ;-) In essence, I am not a C/C++
programmer by trade, hobby, or whatever.

[ virtual array<array<String ^>^> ^GetUnknownRequestHeaders(void) ]

Bravo!  Seriously, you need not be a diehard programmer to make contributions(!)
As far as committership, we have a whole subproject dedicated to the art of
not programming ([EMAIL PROTECTED] ;-) from where there are many committers.

Some additional information regarding the port:

1) ASP.NET 1.x programs will *run* on it quite happily - Windows Server
   Update Services was in business a long time before .NET 2.0 made
   debut. You just can't coerce mod_aspdotnet to *bind* to 1.x Framework
   versions. It really may not make a difference in most scenarios,
   unless MS broke backward compatibility in a very obscure way
   (this of course is purely speculation, but reasonably likely given
   MS's wonderful track record for such things :-P).

Gotcha.  Yes, it's the underlying clr we are talking about, not the versions
of specific apps.  Hopefully, with .NET 2.0 installed, these continue to run.

2) resolve_apache was untouched, but it requires fixing because it will
   not detect Apache 2.2 because it has apache.exe hardcoded as a string
   literal.

Unfortunately it's not that simple :(  Compiled against the httpd-2.0 headers,
we must still resolve apache.exe.  Compiled against the httpd-2.2 headers, we
can resolve httpd.exe.  I'm working on a solution which would install either.

3) The installer project was upgraded to InstallShield 11.5, half by
   accident and half by intent. (Accident: forgot to remove the
   installer project from the solution - Intent: only 11.5 works with
   VS2005)

I'm tripping over these, ya.

Since I have nothing better to do over the next few days, I'll quickly
fill in the CLA and send it off via fax. It doesn't mean I can receive
faxes: there is no ink in the fax machine :-P

Sounds great :)  I'll ack when I've seen it arrive.  With your clue on the
jaggy syntax, we have some hope of merging our work and having this ready
for folks to pick up.

Bill

Reply via email to