Certainly .NET will be here before we know it. Some day, we might find ourselves migrating the scripts that we write today to VB.NET or C#. What can or should we as ASP/Scripting programmers be doing now to reduce future headaches? Anything we can do today to help a future conversion program do its job more painlessly? Certainly, including all the "optional" ASP convention syntax would probably help. Any other ideas?the best practice is <BR><BR>a) be strict with yourself. make sure your code is consistent and documented<BR>b) use PHP instead (my 2 cents)<BR><BR>j
Best practices for future
- Thread starter FALSE
- Start date