|
Thanks for the help 
|
|
|
|
|
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it.
I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected.
I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE.
Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
Because you're not using the integrated tool, you may just have to close the solution, shut down the IDE and then reopen everything again. I've encountered similar behavior when doing this after checking out from subversion. I think the IDE is trying to be "smart" on file permissions.
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
Try undo checkout and then checkout once again.
|
|
|
|
|
As someone else mentioned, you probably need to exit and restart the IDE. VS tends to cache file attributes rather than re-check them every time you want to do something.
You might also want to check that the working folder for the project in SourceSafe is the same folder from which you are opening the file in the IDE.
John Simmons / outlaw programmer wrote: I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE.
I'll probably get flamed for this, but why not?
SourceSafe integrates perfectly well with Visual Studio, as long as you use the latest version of SourceSafe (VSS 2005) with VS2008 and later. Earlier versions still work, but are missing some bug fixes that the later versions of Visual Studio need.
SourceSafe isn't the best source control solution in the world, but it isn't the complete "dog's arse" (as our friends from Oz would put it) that everyone says it is.
Software Zen: delete this;
|
|
|
|
|
The problem is that you converted your project to VB.NET from c#. If you convert it back... everything will work fine
I kid 
|
|
|
|
|
Get rid of Source-Safe and move to Subversion. You will never get the type of issues you are describing...
Besides, Subversion is free...
Steve Naidamast
Black Falcon Software, Inc.
blackfalconsoftware@ix.netcom.com
|
|
|
|
|
Source-Safe is anything but safe. Make sure your data base never gets too big, make sure you never run out of disk space, etc. Actually you should probably memorize these Best Practices.
To me is sounds like running with Scissors would be safer...
|
|
|
|
|
Oh my, I thought it couldn't get worse when you said you had to convert C# to VB...
Now VB + SourceSafe... Oh my, you are F*****!!
Did you start looking for a new job yet?
|
|
|
|
|
Well, that was a big help. Not!
|
|
|
|
|
I would suggest the same as what was already suggested... So no point on that, just commenting on the events
|
|
|
|
|
I have a class library which contains a class called JBXFile which has a save method:
Public Sub Save(ByRef roomInformation As SortedList(Of Decimal, Room))
Save(Me.FilePath, roomInformation)
End Sub
This in turn calls the following method:
Public Sub Save(ByVal filepath As String, ByRef roomInformation As SortedList(Of Decimal, Room))
....
....
End Sub
Now in my main form I try to call this method with JBXFile.Save(Rooms). Rooms is also a sorted list of decimal, room. For some reason though the IDE is giving me an error stating:
Error 5 Reference required to assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' containing the type 'System.Collections.Generic.SortedList`2'. Add one to your project.
I don't understanding why this error is occuring. What is a 'System.Collection.Generic.SortedList`2'. In the form I have a reference to
System
System.Collections
System.Generics
I tried all three to see if it would help. Can you not pass sorted lists as an argument? This has brought my application to a complete halt. Thanks in advanced for any help.
Dominick
|
|
|
|
|
In your form, you either need an appropriate Imports statement e.g.
Imports System.Collections.Generic
or else you need to fully qualify your reference(s) in your code to the SortedList class as System.Collections.Generic.SortedList.
|
|
|
|
|
That looks a bit like a mess. For generic collections you need:
Imports System.Collections.Generic
and no extra reference. All collections are located in the System.dll which is always included.
AFAIK there is no such thing as System.Generics
Are you by any chance mixing different versions of .NET? It can't be done (well there is a small exception, you don't want it, trust me).
Suggestion: do a "clear build", i.e. remove all existing intermediate files such as .obj, actually remove the obj folder(s) of your project, then do a full rebuild.
|
|
|
|
|
My mistake I had a reference to:
System
System.Collections
System.Collections.Generics
However I did notice something about the version numbers. The external assembly as a System.dll version number of 2.0.0.0 while my form application has a System.dll version number of 3.5.0.0. Could this be the problem? If so how would I go about bring my external assembly to version 3.5.0.0 with having to re-write the application? BTW this must have been a severe oversight has I alway target my applications for .NET 3.5.
|
|
|
|
|
Because the external assembly and the form application were using different version of the System.dll I decided to make a new class dll that was targeted to the same version as the form application. However, I'm still getting the same error message. Why is it telling me that I need to reference V2.0.0.0 of the System.dll when both the form application and the class library are using V3.5.0.0 of the System.dll. What am I missing here?
|
|
|
|
|
Okay it has been solved. It had to do with the version of the system dll's not matching. Thanks for the help...I alway target my applications to 3.5 so I don't know why this one was 2.0. It is something I would never have thought to check.
|
|
|
|
|
Glad you got it working.
BTW: replying to your own message gives you a message box ("is this what you really want?") as nobody will get any e-mail notification. One normally replies to someone else's message, and that someone then gets an e-mail...
|
|
|
|
|
Is there any method which will help me to first check a file extention while it is being saved or copied on drive using vb6 or vb.net
Requesting to kindly help me.
|
|
|
|
|
Saving or copying is no different than opening the file for Read access, reading the file, then writing the contents to another file opened for write access. There is no Copy event or hook.
The only way you'd be able to get the file extension of a file being opened for Write access (you cannot determine WHY the file was opened) would be to write a NTFS Filter Driver[^], which you cannot do in VB or VB.NET.
|
|
|
|
|
Do you really want to know the extension of an in-memory file? or you know the path/name of file and just want to extract the extension?!
|
|
|
|
|
Extracting extension of a file is very simple.
What I want is while a File is being copied/saved/opened should be check for its extension.
and If the extention match then it shouldnt copy/save/open that file.
Any Idea??
|
|
|
|
|
I already told you what your only option is. You cannot prevent a file read/write any other way.
|
|
|
|
|
But cant i prevent opening the file???
Like when any user tries to Open the file it will check and then block
|
|
|
|
|
NO! You cannot do this in VB or VB.NET!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
