Best practices for future

Results 1 to 2 of 2

Thread: Best practices for future

  1. #1
    Dudley M Guest

    Default Best practices for future

    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?

  2. #2
    Join Date
    Dec 1969

    Default RE: Best practices for future

    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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts