I'm inclined to agree that you could reasonably have assumed that GRWBSC would want you to use their technology. At the very least they should have been told up front that you weren't planning to. That would give them the option of changing their requirements to be more specific and you the option of re-estimating the time/cost based on the changed requirements.
If you haven't tried PerlEx from ActiveState, you might be pleasantly surprised how easily you can move your apps from Apache to IIS - I know I was. It's not free but your can try it for free and the retail price is probably less than a few hours of your time.
If your application is dependent on MySQL's dialect of SQL, then you could continue to run that on GRWBSC's operating system - NetCraft won't have any visibility on that.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
