Time scope of converting .aspx to .php
Our company uses a .aspx webpage to provide access to a tool called the LIFO calculator. We are moving over to an Apache Linux based server with our migration to wordpress, and are aware we will be loosing the ability to publish the LIFO calculator in its current .aspx form. With our IT guy now being part-time/semi-retired, we were trying to get a feel of what the time commitment would likely be for completing such a rewrite in .php form. I have our IT guys word that he would be able to write the new .php code, but he has no idea how long that may take. He is the same person whom originally created the LIFO Calculator, so he is familiar with the inner-workings of the LIFO Calculator. Could someone familiar with the process of writing .php code based on .aspx language provide a rough estimate of what the time commitment may be (in form of hours; i.e. 50, 200 etc.) for completing this task? I've provided the links to our LIFO calculator tool which should provide some help in getting a feel for the nature and substance of what we are trying to do. The calculator has website compatibility requirements, and instructions on how to set up your internet browser in compatibility mode for the calculator to properly display is shown at this link: LIFO Calculator Compatibility Requirements
This is the .aspx LIFO Calculator page: LIFO Calculator Tool
This is the .aspx LIFO Calculator page: LIFO Calculator Tool
I was going to look at the calculator and let you know what it would require, but it's broken on the site right now.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
http://lifopro.com/LIFOWebCalculatornew.aspx works fine for me in Firefox and IE8. However, any site that talks about compatibility problems with web browsers is talking about old versions of Internet Explorer. Out of thousands of pages that I have written, not one requires 'compatibility settings' in Internet Explorer. All that is being displayed is a simple (though overcomplicated) table with data. There shouldn't be any problem in any browser.
Dave,
ASPX and applets are very different than PHP, and they do require certain settings in order to communicate with the OS at an integration level PHP doesn't offer. I've had to do things like that before, but since moved onto programming in a way which doesn't pigeonhole my code like that.
ASPX and applets are very different than PHP, and they do require certain settings in order to communicate with the OS at an integration level PHP doesn't offer. I've had to do things like that before, but since moved onto programming in a way which doesn't pigeonhole my code like that.
I could best equate it to using namespaces in PHP, where the modules and their functionality which is written into the classes and objects can't migrate into newer versions without a rewrite, and yeah... the modules written on aren't forward compatible either.
ASKER
Guys:
I'm not asking for an analysis of the fact that our current .aspx page has compatibility issues. That fact is known, and will cease to exist if/when the site is converted to a .php page. There are instructions that I CLEARLY pointed out and provided a link that shows step-by-step instruction on how to make the LIFO calculator properly display. What I am asking for is this:
Is there a general idea on how much time it would require our in-house IT staff (1 person) to take the current .aspx site and write it as a .php page? The attached file contains the .aspx webpages source code for the LIFO Calculator
Y--n.e.c-MiscYDriveFiles-Webpage-R-D-LIF
I'm not asking for an analysis of the fact that our current .aspx page has compatibility issues. That fact is known, and will cease to exist if/when the site is converted to a .php page. There are instructions that I CLEARLY pointed out and provided a link that shows step-by-step instruction on how to make the LIFO calculator properly display. What I am asking for is this:
Is there a general idea on how much time it would require our in-house IT staff (1 person) to take the current .aspx site and write it as a .php page? The attached file contains the .aspx webpages source code for the LIFO Calculator
Y--n.e.c-MiscYDriveFiles-Webpage-R-D-LIF
Frank,
I really don't care. I have always considered the ActiveX addons to be a problem since they Only run in IE and there have been many times over the last decade that IE was not the most common or most useful browser. I believe ActiveX is no longer available in IE11 since it became such a security risk.
But even more basically, browser settings really nothing to do with the requirements for generating that table. Somewhere there is a formula or process that could be used in any language to generate that table. And it has nothing to do with compatibility settings.
I really don't care. I have always considered the ActiveX addons to be a problem since they Only run in IE and there have been many times over the last decade that IE was not the most common or most useful browser. I believe ActiveX is no longer available in IE11 since it became such a security risk.
But even more basically, browser settings really nothing to do with the requirements for generating that table. Somewhere there is a formula or process that could be used in any language to generate that table. And it has nothing to do with compatibility settings.
lifopro,
That link is the web page and Not the source code for the calculator part. The calculator code is in the ASPX file on the server. But the browser only receives the results, not the code that does the calculations.
That link is the web page and Not the source code for the calculator part. The calculator code is in the ASPX file on the server. But the browser only receives the results, not the code that does the calculations.
Can you tell us a little more about what the backend script is doing? The front end seems to be JavaScript, right? It looks like there are 13 data elements per year.
ASKER
It is a inventory value calculation using the "LIFO", or Last-In, First Out Method. Columns B & C are editable. You enter your inventory balance ("FIFO Inventory") into Column B, and enter your inflation index ("cur index") into column C, and the LIFO Calculator performs the required computations to populate the results in Columns D through M. This occurs for 1-6 rows, since there are up to 6 years available on the LIFO Calculator that values can be entered for. The light blue shading shows the cells that are available for entering your own values.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ray:
LIFO-PRO uses it as a resource for prospective/current clients wishing to check their LIFO calculations for accuracy.
LIFO-PRO uses it as a resource for prospective/current clients wishing to check their LIFO calculations for accuracy.
ASKER
Thanks for your feedback, Ray. We were fearing this becoming a 200+ hour project; it appears that it would be 200 or less, knock on wood!
I think you're safe with that estimate. Depending on how skillfully you use object-oriented design principles, it could be a lot less! Best regards, ~Ray
http://www.mono-project.com/docs/web/aspnet/