Build 2004 of mod_aspdotnet is prepared (after a number of abortive
attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
along with switching flavors of InstallShield to a version I have installed)
and seeking voters. The update is here;
Please cast your +/- 1's to release
(along with associated binaries 2.0.0.2004.msi and 2.2.0.2004.msi,
one corresponding to 2.0.44 and later, the other to 2.2.2 and later).
This is the last expected release on the Visual Studio .NET (al la 2002)
compiler toolchain; the next effort is porting it to VS 2005 (al la, the
one available in a free flavor). Porting breaks compatibility with the
older tools, since VS 2005's CNET schema is miles beyond 2002. For
example, a reference becomes a reference, not an overloaded psuedo-pointer.
Bill

Jorge Schrauwen wrote:
Well i can't vote but since no-one seem to be replying

FWIW - everyone can vote ;-) It's a matter of the counting that's the
issue. In any case thank you for the testing and your feedback.

x46 e.g. x64 amd build of 2.2.2? You self compiled mod_aspdotnet from the
zip source package? It would be additional useful information.

William A. Rowe, Jr. wrote:
FWIW - everyone can vote ;-) It's a matter of the counting that's the
issue. In any case thank you for the testing and your feedback.
If anyone can vote then +1 from me.
-Daquell

WDaquell wrote:
William A. Rowe, Jr. wrote:
>FWIW - everyone can vote ;-) It's a matter of the counting that's the
>issue. In any case thank you for the testing and your feedback.
If anyone can vote then +1 from me.

Thanks Daquell :) But can you please mention what you reviewed or tested,
so that other PMC members can cast educated votes based on your decision?

Ping to the committee and interested users;

vote began early on 7/7 and will close early on 7/17. Three +1's of the PMC
are required to release this software, with more +'s than -'s. voters
are welcome to chime in with advisory votes to help the PMC.

7/17 the software will be released, or this software will be ejected from
the httpd PMC and the module officially shuttered. This is just your friendly
midpoint reminder.

And after my own review (which I don't until after rolling it), +1 for release.

Bill

William A. Rowe, Jr. wrote:
Build 2004 of mod_aspdotnet is prepared (after a number of abortive
attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
along with switching flavors of InstallShield to a version I have
installed)
and seeking voters. The update is here;

Please cast your +/- 1's to release
(along with associated binaries 2.0.0.2004.msi and 2.2.0.2004.msi,
one corresponding to 2.0.44 and later, the other to 2.2.2 and later).

This is the last expected release on the Visual Studio .NET (al la 2002)
compiler toolchain; the next effort is porting it to VS 2005 (al la, the
one available in a free flavor). Porting breaks compatibility with the
older tools, since VS 2005's CNET schema is miles beyond 2002. For
example, a reference becomes a reference, not an overloaded psuedo-pointer.

Bill

.

Binary looks good on 2.0.58 - runs Windows Server Update Services with
zero problems. Because I'm roughly 10000 km from my test machine (and
will remain so until July 27), I haven't gotten around to testing it on
2.2.2, but I believe there will be no problems on 2.2.x. Can't compile
source either, owing to the fact that I do not have VS.NET 2002
installed on this machine. I give this build my non-binding +1.

To everyone out there, especially the PMC: _please_ don't let
mod_aspdotnet die out so easily mod_aspdotnet is the only hope for
Windows users who despise IIS but do need ASP.NET. :( Throw in your
votes before 7/17 and make the effort to save this module from its Doomsday.