Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Afraid of Another Developer's Code

Afraid of Another Developer's Code

Scheduled Pinned Locked Moved The Lounge
csharphelphtmlcss
21 Posts 11 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A AspDotNetDev

    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. :~

    [WikiLeaks Cablegate Cables]

    S Offline
    S Offline
    Spectre_001
    wrote on last edited by
    #21

    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

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups