The joys of learning on the fly
-
Ya know, don't you just love it when you have an entire team of people counting on you to solve a problem that you have no experience for. Maybe some of you web guys can appreciate my pain now that I know a little more about yours... I'm the Technical Lead for Phase 3 of a 4 phase web project (so far) to make a perfectly good MFC application an internet application for no other reason than to satisfy the whims of a really big company I can't name that think all future applications must be internet apps. Sigh. Now, why I am, a C/C++, ATL, COM, MFC, (VB...bleh) programmer tech leading a web project?! Not sure. Probably because of my experience with the business, the COM side (which is very heavy), and the previous MFC application. At any rate, I know Visual Studio backwards, forwards, left, and right. Interdev is a whole separate story. Well, the previous tech lead didn't have this experience either so I guess it was my turn to get screwed. Our application (web side) exists on our development web server, a Windows 2000 Server running IIS 5.0 and uses FrontPage Extensions so we can use Interdev tied through Source Safe for source ontrol. What a pain. Phase I and II of the project shook out most of these details and Phase 3 was kicking along pretty good till our Corporate Version of Norton updated it's virus definitions, pushed them onto our workstations (and servers) and immediately found a fairly new virus (a worm) that had just started munching it's way through our SourceSafe database. It's so new you can only Quarantine it. There's not even a "cure" yet. SO, our network admin backed up everything (not infected) of our SourceSafe and InetPub directory and formatted the machine... (Even though we had quarantined the infected files, we found it popping up in other places by the next day.) WHAT A PAIN! It took us three days to figure out all the settings necessary to get not only IIS happy but with Windows 2000 you're back to almost Unix-like pain without Unix-like tools where everything is protected.... but far less intuitively. With NT4 you just pretty much made sure your stinkin files weren't Read Only (for our XML files generated from the Sequel 2000 server we're also using). Eventually after resetting the correct permissions about 1 hundred times we realized we had to do this on a folder per folder basis and then there was like a million other problems. Frontpage extensions, for example.... What kind of crap is that?!? Basically you get a bunch of subfolders under your main ones with brilliant names like
-
Ya know, don't you just love it when you have an entire team of people counting on you to solve a problem that you have no experience for. Maybe some of you web guys can appreciate my pain now that I know a little more about yours... I'm the Technical Lead for Phase 3 of a 4 phase web project (so far) to make a perfectly good MFC application an internet application for no other reason than to satisfy the whims of a really big company I can't name that think all future applications must be internet apps. Sigh. Now, why I am, a C/C++, ATL, COM, MFC, (VB...bleh) programmer tech leading a web project?! Not sure. Probably because of my experience with the business, the COM side (which is very heavy), and the previous MFC application. At any rate, I know Visual Studio backwards, forwards, left, and right. Interdev is a whole separate story. Well, the previous tech lead didn't have this experience either so I guess it was my turn to get screwed. Our application (web side) exists on our development web server, a Windows 2000 Server running IIS 5.0 and uses FrontPage Extensions so we can use Interdev tied through Source Safe for source ontrol. What a pain. Phase I and II of the project shook out most of these details and Phase 3 was kicking along pretty good till our Corporate Version of Norton updated it's virus definitions, pushed them onto our workstations (and servers) and immediately found a fairly new virus (a worm) that had just started munching it's way through our SourceSafe database. It's so new you can only Quarantine it. There's not even a "cure" yet. SO, our network admin backed up everything (not infected) of our SourceSafe and InetPub directory and formatted the machine... (Even though we had quarantined the infected files, we found it popping up in other places by the next day.) WHAT A PAIN! It took us three days to figure out all the settings necessary to get not only IIS happy but with Windows 2000 you're back to almost Unix-like pain without Unix-like tools where everything is protected.... but far less intuitively. With NT4 you just pretty much made sure your stinkin files weren't Read Only (for our XML files generated from the Sequel 2000 server we're also using). Eventually after resetting the correct permissions about 1 hundred times we realized we had to do this on a folder per folder basis and then there was like a million other problems. Frontpage extensions, for example.... What kind of crap is that?!? Basically you get a bunch of subfolders under your main ones with brilliant names like
Nice whine, I've felt similar agonies recently setting up a NetWork (Something I have no experience in) Regardz Colin Davies
-
Nice whine, I've felt similar agonies recently setting up a NetWork (Something I have no experience in) Regardz Colin Davies
Fancy Names have got a slight disadvantage! just thought I'd mention it... :suss: maXallion
"I code, therefore I am!" - The Code Devil
www.maxallion.de - coded evil & more -
Ya know, don't you just love it when you have an entire team of people counting on you to solve a problem that you have no experience for. Maybe some of you web guys can appreciate my pain now that I know a little more about yours... I'm the Technical Lead for Phase 3 of a 4 phase web project (so far) to make a perfectly good MFC application an internet application for no other reason than to satisfy the whims of a really big company I can't name that think all future applications must be internet apps. Sigh. Now, why I am, a C/C++, ATL, COM, MFC, (VB...bleh) programmer tech leading a web project?! Not sure. Probably because of my experience with the business, the COM side (which is very heavy), and the previous MFC application. At any rate, I know Visual Studio backwards, forwards, left, and right. Interdev is a whole separate story. Well, the previous tech lead didn't have this experience either so I guess it was my turn to get screwed. Our application (web side) exists on our development web server, a Windows 2000 Server running IIS 5.0 and uses FrontPage Extensions so we can use Interdev tied through Source Safe for source ontrol. What a pain. Phase I and II of the project shook out most of these details and Phase 3 was kicking along pretty good till our Corporate Version of Norton updated it's virus definitions, pushed them onto our workstations (and servers) and immediately found a fairly new virus (a worm) that had just started munching it's way through our SourceSafe database. It's so new you can only Quarantine it. There's not even a "cure" yet. SO, our network admin backed up everything (not infected) of our SourceSafe and InetPub directory and formatted the machine... (Even though we had quarantined the infected files, we found it popping up in other places by the next day.) WHAT A PAIN! It took us three days to figure out all the settings necessary to get not only IIS happy but with Windows 2000 you're back to almost Unix-like pain without Unix-like tools where everything is protected.... but far less intuitively. With NT4 you just pretty much made sure your stinkin files weren't Read Only (for our XML files generated from the Sequel 2000 server we're also using). Eventually after resetting the correct permissions about 1 hundred times we realized we had to do this on a folder per folder basis and then there was like a million other problems. Frontpage extensions, for example.... What kind of crap is that?!? Basically you get a bunch of subfolders under your main ones with brilliant names like
-
Ya know, don't you just love it when you have an entire team of people counting on you to solve a problem that you have no experience for. Maybe some of you web guys can appreciate my pain now that I know a little more about yours... I'm the Technical Lead for Phase 3 of a 4 phase web project (so far) to make a perfectly good MFC application an internet application for no other reason than to satisfy the whims of a really big company I can't name that think all future applications must be internet apps. Sigh. Now, why I am, a C/C++, ATL, COM, MFC, (VB...bleh) programmer tech leading a web project?! Not sure. Probably because of my experience with the business, the COM side (which is very heavy), and the previous MFC application. At any rate, I know Visual Studio backwards, forwards, left, and right. Interdev is a whole separate story. Well, the previous tech lead didn't have this experience either so I guess it was my turn to get screwed. Our application (web side) exists on our development web server, a Windows 2000 Server running IIS 5.0 and uses FrontPage Extensions so we can use Interdev tied through Source Safe for source ontrol. What a pain. Phase I and II of the project shook out most of these details and Phase 3 was kicking along pretty good till our Corporate Version of Norton updated it's virus definitions, pushed them onto our workstations (and servers) and immediately found a fairly new virus (a worm) that had just started munching it's way through our SourceSafe database. It's so new you can only Quarantine it. There's not even a "cure" yet. SO, our network admin backed up everything (not infected) of our SourceSafe and InetPub directory and formatted the machine... (Even though we had quarantined the infected files, we found it popping up in other places by the next day.) WHAT A PAIN! It took us three days to figure out all the settings necessary to get not only IIS happy but with Windows 2000 you're back to almost Unix-like pain without Unix-like tools where everything is protected.... but far less intuitively. With NT4 you just pretty much made sure your stinkin files weren't Read Only (for our XML files generated from the Sequel 2000 server we're also using). Eventually after resetting the correct permissions about 1 hundred times we realized we had to do this on a folder per folder basis and then there was like a million other problems. Frontpage extensions, for example.... What kind of crap is that?!? Basically you get a bunch of subfolders under your main ones with brilliant names like
But look, now your an expert, right? I'm sure your company will give you all these plum assignments in the future. And if you need therapy, you can always come to the lounge. We'll tell you what's wrong with you. :)
-
Ya know, don't you just love it when you have an entire team of people counting on you to solve a problem that you have no experience for. Maybe some of you web guys can appreciate my pain now that I know a little more about yours... I'm the Technical Lead for Phase 3 of a 4 phase web project (so far) to make a perfectly good MFC application an internet application for no other reason than to satisfy the whims of a really big company I can't name that think all future applications must be internet apps. Sigh. Now, why I am, a C/C++, ATL, COM, MFC, (VB...bleh) programmer tech leading a web project?! Not sure. Probably because of my experience with the business, the COM side (which is very heavy), and the previous MFC application. At any rate, I know Visual Studio backwards, forwards, left, and right. Interdev is a whole separate story. Well, the previous tech lead didn't have this experience either so I guess it was my turn to get screwed. Our application (web side) exists on our development web server, a Windows 2000 Server running IIS 5.0 and uses FrontPage Extensions so we can use Interdev tied through Source Safe for source ontrol. What a pain. Phase I and II of the project shook out most of these details and Phase 3 was kicking along pretty good till our Corporate Version of Norton updated it's virus definitions, pushed them onto our workstations (and servers) and immediately found a fairly new virus (a worm) that had just started munching it's way through our SourceSafe database. It's so new you can only Quarantine it. There's not even a "cure" yet. SO, our network admin backed up everything (not infected) of our SourceSafe and InetPub directory and formatted the machine... (Even though we had quarantined the infected files, we found it popping up in other places by the next day.) WHAT A PAIN! It took us three days to figure out all the settings necessary to get not only IIS happy but with Windows 2000 you're back to almost Unix-like pain without Unix-like tools where everything is protected.... but far less intuitively. With NT4 you just pretty much made sure your stinkin files weren't Read Only (for our XML files generated from the Sequel 2000 server we're also using). Eventually after resetting the correct permissions about 1 hundred times we realized we had to do this on a folder per folder basis and then there was like a million other problems. Frontpage extensions, for example.... What kind of crap is that?!? Basically you get a bunch of subfolders under your main ones with brilliant names like
perfectly good MFC app that must become an Internet app, today.... i'm in the same (sinking) boat. yuck. -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com
-
perfectly good MFC app that must become an Internet app, today.... i'm in the same (sinking) boat. yuck. -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com
Isn't it enough to use WebBrowser control in the about box? :) Cheers, Tomasz Sowinski -- http://www.shooltz.com.pl
-
Ya know, don't you just love it when you have an entire team of people counting on you to solve a problem that you have no experience for. Maybe some of you web guys can appreciate my pain now that I know a little more about yours... I'm the Technical Lead for Phase 3 of a 4 phase web project (so far) to make a perfectly good MFC application an internet application for no other reason than to satisfy the whims of a really big company I can't name that think all future applications must be internet apps. Sigh. Now, why I am, a C/C++, ATL, COM, MFC, (VB...bleh) programmer tech leading a web project?! Not sure. Probably because of my experience with the business, the COM side (which is very heavy), and the previous MFC application. At any rate, I know Visual Studio backwards, forwards, left, and right. Interdev is a whole separate story. Well, the previous tech lead didn't have this experience either so I guess it was my turn to get screwed. Our application (web side) exists on our development web server, a Windows 2000 Server running IIS 5.0 and uses FrontPage Extensions so we can use Interdev tied through Source Safe for source ontrol. What a pain. Phase I and II of the project shook out most of these details and Phase 3 was kicking along pretty good till our Corporate Version of Norton updated it's virus definitions, pushed them onto our workstations (and servers) and immediately found a fairly new virus (a worm) that had just started munching it's way through our SourceSafe database. It's so new you can only Quarantine it. There's not even a "cure" yet. SO, our network admin backed up everything (not infected) of our SourceSafe and InetPub directory and formatted the machine... (Even though we had quarantined the infected files, we found it popping up in other places by the next day.) WHAT A PAIN! It took us three days to figure out all the settings necessary to get not only IIS happy but with Windows 2000 you're back to almost Unix-like pain without Unix-like tools where everything is protected.... but far less intuitively. With NT4 you just pretty much made sure your stinkin files weren't Read Only (for our XML files generated from the Sequel 2000 server we're also using). Eventually after resetting the correct permissions about 1 hundred times we realized we had to do this on a folder per folder basis and then there was like a million other problems. Frontpage extensions, for example.... What kind of crap is that?!? Basically you get a bunch of subfolders under your main ones with brilliant names like
I've had the misfortune of late to find myself using applications which *should* have been written as windows desktop apps, but were instead written as web apps. My evaluation: They Suck. They will always suck. No amount of software engineering genius will ever make them not suck. Its like some kind of marketing/managment conspiracy to make software suck. Can anyone give me an example of a web based application which does not suck?
-
perfectly good MFC app that must become an Internet app, today.... i'm in the same (sinking) boat. yuck. -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com
-
I've had the misfortune of late to find myself using applications which *should* have been written as windows desktop apps, but were instead written as web apps. My evaluation: They Suck. They will always suck. No amount of software engineering genius will ever make them not suck. Its like some kind of marketing/managment conspiracy to make software suck. Can anyone give me an example of a web based application which does not suck?
-
Ya know, don't you just love it when you have an entire team of people counting on you to solve a problem that you have no experience for. Maybe some of you web guys can appreciate my pain now that I know a little more about yours... I'm the Technical Lead for Phase 3 of a 4 phase web project (so far) to make a perfectly good MFC application an internet application for no other reason than to satisfy the whims of a really big company I can't name that think all future applications must be internet apps. Sigh. Now, why I am, a C/C++, ATL, COM, MFC, (VB...bleh) programmer tech leading a web project?! Not sure. Probably because of my experience with the business, the COM side (which is very heavy), and the previous MFC application. At any rate, I know Visual Studio backwards, forwards, left, and right. Interdev is a whole separate story. Well, the previous tech lead didn't have this experience either so I guess it was my turn to get screwed. Our application (web side) exists on our development web server, a Windows 2000 Server running IIS 5.0 and uses FrontPage Extensions so we can use Interdev tied through Source Safe for source ontrol. What a pain. Phase I and II of the project shook out most of these details and Phase 3 was kicking along pretty good till our Corporate Version of Norton updated it's virus definitions, pushed them onto our workstations (and servers) and immediately found a fairly new virus (a worm) that had just started munching it's way through our SourceSafe database. It's so new you can only Quarantine it. There's not even a "cure" yet. SO, our network admin backed up everything (not infected) of our SourceSafe and InetPub directory and formatted the machine... (Even though we had quarantined the infected files, we found it popping up in other places by the next day.) WHAT A PAIN! It took us three days to figure out all the settings necessary to get not only IIS happy but with Windows 2000 you're back to almost Unix-like pain without Unix-like tools where everything is protected.... but far less intuitively. With NT4 you just pretty much made sure your stinkin files weren't Read Only (for our XML files generated from the Sequel 2000 server we're also using). Eventually after resetting the correct permissions about 1 hundred times we realized we had to do this on a folder per folder basis and then there was like a million other problems. Frontpage extensions, for example.... What kind of crap is that?!? Basically you get a bunch of subfolders under your main ones with brilliant names like
Hello, the codegurus around the world.;) Well, the problem solving skill is very important to survive the programmer.:cool: Sometimes, we can't find any answers of the bug by any materails. So, try to debug the code, OS settig, or whatever, and find the solution to get the money. X| Otherwise, change your job except the programmer. :(( If we can do this, we can survive as the programmer.:cool: This is true, I think. Have a nice day!
-Masaaki Onishi-
-
Hello, the codegurus around the world.;) Well, the problem solving skill is very important to survive the programmer.:cool: Sometimes, we can't find any answers of the bug by any materails. So, try to debug the code, OS settig, or whatever, and find the solution to get the money. X| Otherwise, change your job except the programmer. :(( If we can do this, we can survive as the programmer.:cool: This is true, I think. Have a nice day!
-Masaaki Onishi-
Hi Masaaki, You really like smileys - huh? Christian Skovdal Andersen