Board index » Visual Studio » Protect Working Projects

Visual Studio162
I am in the process of making major changes to a program that has

worked for us very well for the last 4 years. I tried to isolate the

working project on external drive :E...

Is it my imagination or are my upgrades to the main project copying

over to my "isolated" project on (:E) as well? I need to solve this

before moving on.



Thank you,

Dave


-

Dave <davegp2@msn.com>'s wild thoughts were released on Fri,

03 Aug 2007 07:44:11 -0700 bearing the following fruit:



Huh?

--

Jan Hyde



https://mvp.support.microsoft.com/profile/Jan.Hyde

-

"Dave" <davegp2@msn.com>wrote

Open the project's *.vbp file in notepad and see what files it

loads for your different modules....



LFS





-

Dave:



When I am in that situation I make sure that I peek into the VBP file

with Notepad and verify that nothing refers to the "safe place" I put

the working project.



Depending on how you "saved" the project ("Save As..." opposed to just

copying) this will tell you if any changes made to the "current" project

will affect the "archived" project.



Other people have other schemes, but this works for me.



GP





--->

On Aug 3, 9:49 am, "Jan Hyde (VB MVP)"

<StellaDrin...@REMOVE.ME.uboot.com>wrote:

Thank you, that was a big help.



-

On Aug 3, 9:52 am, "Larry Serflaten" <serfla...@usinternet.com>wrote:

Thank you Larry, that WAS a big help.

Dave



-

On Aug 3, 9:53 am, Grand_Poobah <iss_boss.del...@delete.sbcglobal.net>

wrote:

Thank you GP, that was a great help too.

Dave



-

"Dave" <davegp2@msn.com>wrote in message



You gave very little information. Some folks guessed at what you were

talking about. Jan gave you a response that was worth about as much as the

input you provided.





-

"Dave" <davegp2@msn.com>wrote in message

If available, immediately install if not already installed and invoke VSS.



Even if the problem is a temporary missdirection of a file or two and thus

easily repaired for now - Sooner or later using your kind of "back-up"

scheme is certain to either repeat the problem or lose something. Create a

new VSS database, and store it on the E: drive if you want.



If you don't have VSS, try this free SCCS:

www.wincvs.org/download.html">www.wincvs.org/download.html

www.tortoisecvs.org/">www.tortoisecvs.org/



Just a suggestion. (Yeah, I know. Big Help. <g>)

-ralph







-

Thank you Ralph, it is.

Dave



-

"Jeff Johnson" <i.get@enough.spam>'s wild thoughts were

released on Fri, 3 Aug 2007 11:31:07 -0400 bearing the

following fruit:



GIGO ;-)

--

Jan Hyde



https://mvp.support.microsoft.com/profile/Jan.Hyde

-

I simply zip up all the files in the project folder, and copy the zip to a

backup directory (or drive). Name each zip for the version backed up, and

you can have a history of all changes very easily.



--

Regards,



Rick Raisley



"Dave" <davegp2@msn.com>wrote in message



-

"Dave" <davegp2@msn.com>wrote in message

Adding to the pile... after checking to make sure your VBP's not setup to

write to your "isolated" project(s), you can use ComGuard to create Project

Snapshots at any time you want. This comes in handy with or without Source

Safe. During the creation, you can place a check in a box and it'll gather

all dependencies as well... once you select a "home" for these snapshots

(default is project folder) it'll place these snapshots in time-stamped

folders and you can use several utilities to do side by side comparisons any

time you want.



It's shareware and the unregistered version has a "nag screen", but it's

fully functional.

www.vbsight.com/ComGuard.htm">www.vbsight.com/ComGuard.htm



If you want, you can set it to create these snapshots every time you

compile... personally, I have it prompt me. It'll also backup the current

binary before over-writing it, if you want.





--

Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..

In Loving Memory - www.vbsight.com/Remembrance.htm">www.vbsight.com/Remembrance.htm





-

Ken and Rick and all helpful posters, thank you.



Dave



-

"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com>wrote in message

Always a good idea.



Add to the pile, if you get bitten by an less known "feature" of the Windows

Shell thru Windows Explorer. If you have a registered component and move it

using the Explorer, Windows will often very kindly re-register the component

at the new location, including the Recycle Bin if you delete it.



The result can often be surprising if you're not expeciting it.



-ralph





-

On Aug 3, 10:31 am, "Jeff Johnson" <i....@enough.spam>wrote:

No, I think you're wrong...some people like to help and some people

like to insult.

Dave



-

Dave <davegp2@msn.com>wrote:

Wow. Okay, "Dave", consider yourself on the persona non grata list from here on

out, given your wont to insult. (You *obviously* don't stop to look around or think

before pressing Send!)

--

.NET: It's About Trust!

vfred.mvps.org">vfred.mvps.org





-

Gee Karl, all the time I thought I was the insultee, not the insultor.

Dave







-

Okay, deep breath here people. Yes, the original post might have been a

little confusing, but "Huh?" doesn't exactly clarify what the source of

confusion is. Things got off to a bad start, and spiraled insanely out of

control in a VERY few messages. Let's not tear each others heads off just

because of the limitations of a text medium.







Rob





-

Dave <davegp2@msn.com>wrote:

Recognizing the problem is the first step in fixing it.

--

.NET: It's About Trust!

vfred.mvps.org">vfred.mvps.org





-

"Ralph" <nt_consulting64@yahoo.com>wrote in message

Tell me about it <g>When we started using VB5 and creating activeX dlls, we

had to "re-train" our test engineers.... they used to select a dll, and hit

the delete button, sending it to the bin... then, just copy the new dll in

its place, expecting it to "work"... well, after we found that they were

reporting the same bug we just finished fixing and/or everything worked fine

until the customer emptied the bin, we realized what was happening <g>...



From now on, guys, "copy and never move or delete!" that dll to a history

folder and copy the new version, over-writing the old version. If the

interface doesn't change, there's no need to re-register... after testing,

go to the history folder and delete the old version....



fwiw, we also associate Regsvr32 with ocx's and dll's, so the test guys can

just double-click to register something.



--

Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..

In Loving Memory - www.vbsight.com/Remembrance.htm">www.vbsight.com/Remembrance.htm





-

Dave <davegp2@msn.com>'s wild thoughts were released on Fri,

03 Aug 2007 13:01:27 -0700 bearing the following fruit:



I've reread every post in this thread and I can't locate a

single insult posted by anyone other than you.



As Karl said you are expected to look around before you

post. If you had you would know that some of us have very

little time and responding *at all* to such an unclear post

was a courtesy not an insult.



Furthemore you'd also be aware my posts are often brief,

prefering to lead the OP towards research or asking

questions or providing more detail.



There is nothing more frustrating that spending an age

researching and providing an answer only for the OP to post

back and say 'that's not what I meant'



All in all you need to be less sensitive and be more careful

with the tone of you own posts. This is a fantastic resource

with fantastic (but very busy) people and it's very very

easy to get yourself added to kill filters.



As someone else pointed out, one can get the wrong end of

the stick in a text only medium. If you think I'm the type

to dish out instults then simply google my name and see if

you still really believe that.



Regards



Jan





--

Jan Hyde



https://mvp.support.microsoft.com/profile/Jan.Hyde

-

Jan,



My apology for my original response to you.



However, there were some very good responses in this thread

considering the lack of information you said I provided in the OP. I

will try and be more concise in my future requests for help. I know

the people responding here are very busy and only trying to help.



Best Regards,

Dave



-