Visual Studio 2005 changed file save not recognized by EDPro

General questions about using ExamDiff Pro, ideas for new features, bug reports, and usage tips.
Post Reply
NSmith
New Member
Posts: 3
Joined: Tue Jan 26, 2010 11:40 am

Visual Studio 2005 changed file save not recognized by EDPro

Post by NSmith »

I use Visual Studio 2005 (VS05) as my programming environment. When I am creating a new version of a file, I will have an EDPro file comparison window open that compares the old file version in my previous release directory to the new file version in my development directory. When I use VS05 to save a change in the file to the copy in the development directory, EDPro doesn't recognize that the file has changed. If I force a re-compare, EDPro then recognizes that the file has changed and produces a new comparison with the old version in the previous release directory. If I open the development file in TextPad, make a change and then save it, EDPro recognizes that the file has changed and asks if I want to do a re-compare. When either VS05 or TextPad saves the changed file, I see the file's size and date stamp change in the development directory, but EDPro doesn't react to the change in the file's status when it was saved by VS05. Has anyone else had this problem? I can't say at what version of EDPro (or VS05 patch) that this problem started occurring, but has become a real productivity slow down. Any help will be greatly appreciated. Thanks.

N. Smith
NSmith
New Member
Posts: 3
Joined: Tue Jan 26, 2010 11:40 am

Re: Visual Studio 2005 changed file save not recognized by EDPro

Post by NSmith »

Here is some additional data. I uninstalled EDPro, and then installed Version 3.5 (from edpro35.exe with creation date 10/10/07 on my computer -- no file version in Properties window). This version works with Visual Studio 2005, and it recognizes when VS05 saves a changed file and asks if I want to do a re-compare.

I then uninstalled EDPro 3.5 from my computer and installed EDPro Version 4.5 from edpro45.exe (File version 4.5.2.2 with creation date 06/02/09 from the properties window). This version of EDPro does not recognize a changed file saved by VS05.

I repeated the uninstall process, and installed the EDPro 5.0 beta version. It also does not recognize a changed file saved by VS05.

I do not have a saved edpro40.exe to see if it also has this problem, and I can't find an archived version on the EDPro web site.

Thanks,

N. Smith
User avatar
psguru
Site Admin
Posts: 2396
Joined: Sat May 15, 2004 4:23 pm
Location: California
Contact:

Re: Visual Studio 2005 changed file save not recognized by EDPro

Post by psguru »

Version 4.5 and up uses a new, more precise, directory change notifications API. However, it so happens that VS2005 has a very odd way of saving files, and this new and improved mechanism fails in such cases (VS2008 works fine). The good news is that the problem will be fixed in the build of 5.0 Beta.
I do not have a saved edpro40.exe to see if it also has this problem, and I can't find an archived version on the EDPro web site.
4.0 can be download here: http://www.prestosoft.com/edp_download_more.asp
psguru
PrestoSoft
NSmith
New Member
Posts: 3
Joined: Tue Jan 26, 2010 11:40 am

Re: Visual Studio 2005 changed file save not recognized by EDPro

Post by NSmith »

Thanks for the link to the previous 4.0 ExamDiff Pro version. It cured my Visual Studio 2005 problem. I did have to do an uninstall of Version 4.5, shutdown, reboot and then install Version 4.0 for the install of Version 4.0 to "take". Some of my colleagues had been pretty sure that the problem was with VS05 and Microsoft not obeying their own API rules. I'm looking forward to a Version 5.0 that does fix the problem. The 5.0 beta from several days ago when I reported this problem still had this problem with VS05 saves. Thanks again.

N. Smith
User avatar
psguru
Site Admin
Posts: 2396
Joined: Sat May 15, 2004 4:23 pm
Location: California
Contact:

Re: Visual Studio 2005 changed file save not recognized by EDPro

Post by psguru »

The latest build of 5.0 (5.0.0.5) contains the fix.
psguru
PrestoSoft
Post Reply