Afraid of Another Developer's Code
-
Walt Fair, Jr. wrote:
Maybe you could send it to someone who says "SND CODEZ PLZ!!!!!"
It's on its way to your inbox. ;P
Great! It works fine, as best I could tell. Feel free to use it on your production system ASAP. No need for further testing.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Great! It works fine, as best I could tell. Feel free to use it on your production system ASAP. No need for further testing.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
You would have made a fortuen as a professional comedian/politician/salesman* (*select as appropriate)
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC League Table Link CCC Link[^]
-
So I just spent the last 2 days trying to get a Visual Studio solution to compile. It's a WPF app that was written in Visual Studio 2008 using third party libraries (for Zip files and for WPF controls). Seems the developer who wrote the code forgot to include the third party libraries (one open source but outdated, the other outdated and requiring an expensive license). I need to modify this app, so I forged ahead. First, I replaced the Zip library reference to the most recent version of the DLL, which I found online. That caused a bunch of errors, which I fixed later, after addressing other inexplicable errors. Then I realized I needed to upgrade to Visual Studio 2010 in order to make use of the built-in DataGrid and other WPF controls. After doing that, the EDMX file (Entity Framework related) caused all kinds of havoc, so I had to manually modify the designer file until things seemed to work. Then I found each third party data grid and date picker and replaced them with their built-in counterparts. At one point, I had to create a new solution to put select projects in, because Visual Studio decided it wanted to compile projects that depended on the current project I was compiling (WTF?). After 2 days of work, I finally got the bugger to compile without any errors or warnings. The only plus side is that it was built using C# (most of my work is currently focused on VB.net). Only problem is I'm sure I broke a few things along the way, but I can fix them until I run the application. And considering this application was built to migrate data to production servers, I'm afraid to even run it. Maybe I should make sure all appropriate backups are setup properly before I flip the switch. In the very least, I think I'll disconnect my network cable first. :~
Hell, I'm afraid of MY code! Marc
-
Hell, I'm afraid of MY code! Marc
Marc - we're all afraid of your code. It makes our heads hurt just looking at it.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
-
You would have made a fortuen as a professional comedian/politician/salesman* (*select as appropriate)
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC League Table Link CCC Link[^]
Dalek Dave wrote:
comedian/politician/salesman
what's the difference?
-
So I just spent the last 2 days trying to get a Visual Studio solution to compile. It's a WPF app that was written in Visual Studio 2008 using third party libraries (for Zip files and for WPF controls). Seems the developer who wrote the code forgot to include the third party libraries (one open source but outdated, the other outdated and requiring an expensive license). I need to modify this app, so I forged ahead. First, I replaced the Zip library reference to the most recent version of the DLL, which I found online. That caused a bunch of errors, which I fixed later, after addressing other inexplicable errors. Then I realized I needed to upgrade to Visual Studio 2010 in order to make use of the built-in DataGrid and other WPF controls. After doing that, the EDMX file (Entity Framework related) caused all kinds of havoc, so I had to manually modify the designer file until things seemed to work. Then I found each third party data grid and date picker and replaced them with their built-in counterparts. At one point, I had to create a new solution to put select projects in, because Visual Studio decided it wanted to compile projects that depended on the current project I was compiling (WTF?). After 2 days of work, I finally got the bugger to compile without any errors or warnings. The only plus side is that it was built using C# (most of my work is currently focused on VB.net). Only problem is I'm sure I broke a few things along the way, but I can fix them until I run the application. And considering this application was built to migrate data to production servers, I'm afraid to even run it. Maybe I should make sure all appropriate backups are setup properly before I flip the switch. In the very least, I think I'll disconnect my network cable first. :~
-
Dalek Dave wrote:
comedian/politician/salesman
what's the difference?
One of them has a job to make you laugh.
-
Dalek Dave wrote:
comedian/politician/salesman
what's the difference?
-
You would have made a fortuen as a professional comedian/politician/salesman* (*select as appropriate)
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC League Table Link CCC Link[^]
Well, I'm not quitting my day job!
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
So I just spent the last 2 days trying to get a Visual Studio solution to compile. It's a WPF app that was written in Visual Studio 2008 using third party libraries (for Zip files and for WPF controls). Seems the developer who wrote the code forgot to include the third party libraries (one open source but outdated, the other outdated and requiring an expensive license). I need to modify this app, so I forged ahead. First, I replaced the Zip library reference to the most recent version of the DLL, which I found online. That caused a bunch of errors, which I fixed later, after addressing other inexplicable errors. Then I realized I needed to upgrade to Visual Studio 2010 in order to make use of the built-in DataGrid and other WPF controls. After doing that, the EDMX file (Entity Framework related) caused all kinds of havoc, so I had to manually modify the designer file until things seemed to work. Then I found each third party data grid and date picker and replaced them with their built-in counterparts. At one point, I had to create a new solution to put select projects in, because Visual Studio decided it wanted to compile projects that depended on the current project I was compiling (WTF?). After 2 days of work, I finally got the bugger to compile without any errors or warnings. The only plus side is that it was built using C# (most of my work is currently focused on VB.net). Only problem is I'm sure I broke a few things along the way, but I can fix them until I run the application. And considering this application was built to migrate data to production servers, I'm afraid to even run it. Maybe I should make sure all appropriate backups are setup properly before I flip the switch. In the very least, I think I'll disconnect my network cable first. :~
Have your DBA make a test copy of the production database on another server. Do your test import to the new test database. This database can then be deleted after testing.
Kevin Rucker, Application Programmer QSS Group, Inc. United States Coast Guard OSC Kevin.D.Rucker@uscg.mil "Programming is an art form that fights back." -- Chad Hower