• (cs) in reply to bimbo69
    Anonymous:

    WRONG! Where are non-US companies ?

    Erm, not in fortune500, AFAIK.

  • captcha=tango (unregistered) in reply to Shizzle

    Anonymous:
    My point was Java has everythign you need, and "upgrading" a Java application to .NET isn't really much of an upgrade, and is almost guaranteed to be more a pain in the butt that it is worth.  I have no problem using someone else's code, I just prefer to be able to pick what code I'm going to use.  Java has plenty of frameworks both free and for sale out there, but as far as I have seen, with .NET you are stuck mostly with Microsoft's vision on how things are supposed to work.

    There are plenty of free and commercial frameworks for .NET too but for the most part you don't need them because they're built-in and are supported by a billion dollar company.

  • Dean Cleaver (unregistered)

    Many are saying "search and replace". That's great for single lines of code. Doesn't work when they have the same javascript blocks in 33 pages, and call it from just one. Also doesn't work when 33 pages have 33 different style sheets - or at least 33 different paths to the same sheet name - search and replace is simply not a viable solution to that problem.

    Of the 123 style sheets, they were all named the same and in different folders, but many of them had been changed. So it wasn't just a case of "stick them all in one folder and S&R the css in the pages" - you think I don't know that trick already? 23 years of programming experience, I do know what I'm doing. I basically had to windiff every css in every folder, compare them, and try to create a "master" with all the extra bits from every file added.

    The original JSP site was written by an outside company - because we didn't have access to the source, that's why my predecessor screen scraped it. If he had the source, I'm sure he would have made a tidier mess of it. So this isn't about conversion of JSP to ASP.Net - it's about screen-scraping what just happened to be a JSP site into ASP.Net.

    And perhaps I should add that I was there on contract to do specific jobs on this site - not to fix it, but I ended up having to. In my own time. At my expense. As several people have suggested I should have. I just didn't want to hang around trying to get blood out of a stone - they had a budget of between $1 and $2, and wanted a Rolls Royce for that money...

  • (cs) in reply to I don't Get it
    Anonymous:
    why not go for broke and tell him its stupid.


    Because it doesnt work most of the time. It does depend on the manager, but a lot aren't their because of their skill in the type of work that's being done. Most are their because they can manage money and be political.

    I've had my fair share of bosses that havent a clue, but they know what they want. You can put your point in when they dont know what they want, but if they've seen or heard of something, theirs no changing their mind. eg, one guy I worked for heard about a particular program, and I spent 2 minutes trying the demo, 3 minutes looking for a free thing, found one exactly the same but written in Java and didnt export to Word docs (did export to HTML though), showed the boss, and he still wanted the $100 per license version.
  • Just Me (unregistered) in reply to home homine lupus est

    I know about wget and it's also available for Windows as a stand-alone binary (haven't used it much since I don't use Windows anywhere so I don't know if it's 1:1 to *nixes wget)...

  • (cs) in reply to Just Me
    Anonymous:
    I don't know if it's 1:1 to *nixes wget)...
    It is as far as I can tell (at least the one I have is)
  • (cs) in reply to Dean Cleaver
    Anonymous:

    The original JSP site was written by an outside company - because we didn't have access to the source, that's why my predecessor screen scraped it. If he had the source, I'm sure he would have made a tidier mess of it. So this isn't about conversion of JSP to ASP.Net - it's about screen-scraping what just happened to be a JSP site into ASP.Net.

    In a particularly awful way. Though it could be worse - he could've done it on a site that used frames (if he did, IE would've saved the HTML of all the frames in the _files folder, then created new subfolders for the contents of each frame...)

Leave a comment on “Enterprise Conversion Quirks”

Log In or post as a guest

Replying to comment #:

« Return to Article