headers
Shaw Terwilliger | 15 Dec 2004 18:45
Favicon

This Mailing List is Going Away

In January 2004, SourceGear established a support web site to host
community support and discussion forums for its Vault, SourceOffSite,
and SourceOffSite Collab products, as well as its premium Gold support
resource.  With over 1200 active users, and more than 34,000 visitors 
(by unique IP) in 2004, SourceGear considers this web site a big success.

This web site can be reached at http://support.sourcegear.com/

The Vault, SourceOffSite, and SourceOffSite Collab mailing lists 
hosted at lists.sourcegear.com now average fewer than 5 messages per 
month, each.  In order to unify support efforts, these mailing lists
will shut down on December 17, 2004.

Some list members have expressed a desire to have their e-mail 
addresses removed from our web-accessible list archives, which was not 
possible without modifying the mailing list software.  We sympathize 
with those members, because we all get a lot of spam too.  For this 
reason, we plan to remove the list archives from the web site.
Our new support web site offers much better privacy than the
mailing lists (your e-mail address is never made public unless you
place it on your profile page).

Because the list archives still get many hits each month, we're
exploring ways to keep the content protected from robots that harvest
addresses, yet still be available at their original URLs.  If this
service is offered, check the support web site for notification.

The support web site offers an RSS feed for each of the forums, so you 
can have support content delivered to your desktop instead of visiting
the site each day.  For more details on the RSS feeds, read:
(Continue reading)

Permalink | Reply | 0 comments |
headers
dave wanta | 15 Nov 2004 16:47

problem changing/opening repositories

hi all,
I was hoping you could help me with this problem, as I'm dead in the water on this project until I can fix this.
 
I have a number of repositories that I connect to with VS.NET. They are all set by default, so when I open an existing project, it opens the correct repository by default (i think this is the issue here...), and I never have any problems.
 
So, in one solution, I had to branch.  So I branched using Vault Client. No problems. So now I go to VS.NET (2002), create a new solution, and select "open from source control", as I want to open the branch. The SourceGear Vault dialog opens with a list of folders under a repository ($). The problem is that it's not the repository ($) I want. However, I cannot find the option to change repositories. Any suggestions?
 
(I'm speculating below, so feel free to tell me the correct way to fix this)
Now, I think I know how to fix it, I just don't know where.
 
When VS.NET connected to vault, it never prompted me for a login prompt. I think that's because along the way I was asked to accept some defaults, and I did. Hence VS is opening up this "default" repository.  If I can some how get this login dialog back, I think I'll be able to change repositories. So how do I get this login dialog back?!?!
 
Thanks,
Dave
Permalink | Reply | 1 comment |
headers
Renato Carvalho Tereza | 12 Oct 2004 02:27
Picon
Favicon

Error when trying to logging into on my VaultServer

Hi there!

I need help to understand the error described below. I couldn't access my 
VaultServer.

Could someone help me out please?

Thanks in advance for any help.

Cheers,

Renato Carvalho Tereza (Software Developer)
http://www.infosolutions.com.br

Here goes the error message:

Unable to connect to http://localhost/VaultService.  No server was found at 
the specified URL.  Web Exception: Client found response content type of 
'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
    <head>
        <title>!&quot;ValueType mismatch&quot;</title>
        <style>
        	body {font-family:"Verdana";font-weight:normal;font-size: 
.7em;color:black;}
        	p {font-family:"Verdana";font-weight:normal;color:black;margin-top: 
-5px}
        	b {font-family:"Verdana";font-weight:bold;color:black;margin-top: 
-5px}
        	H1 { 
font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
        	H2 { 
font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
        	pre {font-family:"Lucida Console";font-size: .9em}
        	.marker {font-weight: bold; color: black;text-decoration: none;}
        	.version {color: gray;}
        	.error {margin-bottom: 10px;}
        	.expandable { text-decoration:underline; font-weight:bold; 
color:navy; cursor:hand; }
        </style>
    </head>

    <body bgcolor="white">

            <span><H1>Server Error in '/VaultService' Application.<hr 
width=100% size=1 color=silver></H1>

            <h2> <i>!&quot;ValueType mismatch&quot;</i> </h2></span>

            <font face="Arial, Helvetica, Geneva, SunSans-Regular, 
sans-serif ">

            <b> Description: </b>An unhandled exception occurred during the 
execution of the current web request. Please review the stack trace for more 
information about the error and where it originated in the code.

            <br><br>

            <b> Exception Details: </b>System.BadImageFormatException: 
!&quot;ValueType mismatch&quot;<br><br>

            <b>Source Error:</b> <br><br>

            <table width=100% bgcolor="#ffffcc">
               <tr>
                  <td>
                      <code>

An unhandled exception was generated during the execution of the current web 
request. Information regarding the origin and location of the exception can 
be identified using the exception stack trace below.</code>

                  </td>
               </tr>
            </table>

            <br>

            <b>Stack Trace:</b> <br><br>

            <table width=100% bgcolor="#ffffcc">
               <tr>
                  <td>
                      <code><pre>

[BadImageFormatException: !&quot;ValueType mismatch&quot;]
   VaultService.Global.Application_Start(Object sender, EventArgs e) +0
</pre></code>

                  </td>
               </tr>
            </table>

            <br>

            <hr width=100% size=1 color=silver>

            <b>Version Information:</b>&nbsp;Microsoft .NET Framework 
Version:2.0.40607.16; ASP.NET Version:2.0.40607.16

            </font>

    </body>
</html>
<!--
[BadImageFormatException]: !&quot;ValueType mismatch&quot;
   at VaultService.Global.Application_Start(Object sender, EventArgs e)
-->
--.

_________________________________________________________________
MSN Messenger: instale grátis e converse com seus amigos. 
http://messenger.msn.com.br
Permalink | Reply | 1 comment |
headers
Michael Gerfen | 14 Sep 2004 00:32

<vaultgetfile/> fails

Hi,

When I attempt to use the <vaultgetfile/> task I get the this error[1].  I've debugged the code in
VaultBase.IsVaultFolder.  The task fails on this line:

vaultClientFolder = ClientInstance.TreeCache.Repository.Root.FindFolderRecursive(normalizedPath);

because ClientInstance.TreeCache is a null reference.  I've done quite a bit of research in the list
archives but have not come across a cause and solution for this problem.  I have tried to have all of the
CacheMember_ files recreated by deleting them from the ..\ Application
Data\SourceGear\Vault_1\Client\... directory but this has had no effect.

Anyone have any ideas on how to solve this problem?

Thanks,

Michael

[1] Error out from NAnt:

INTERNAL ERROR

System.NullReferenceException: Object reference not set to an instance of an object.
   at NAnt.Contrib.Tasks.SourceGearVault.VaultBase.IsVaultFolder(String folderName) in
c:\nant\vault\vaultbase.cs:line 1
41
   at NAnt.Contrib.Tasks.SourceGearVault.VaultGetFile.GetFile(String fileName) in
C:\Nant\vault\VaultGetFile.cs:line 129

   at NAnt.Contrib.Tasks.SourceGearVault.VaultGetFile.ExecuteTask() in
C:\Nant\vault\VaultGetFile.cs:line 111
   at NAnt.Core.Task.Execute() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp1CE1.tmp\src\NAnt.Core\Task.
cs:line 177
   at NAnt.Core.Target.Execute() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp1CE1.tmp\src\NAnt.Core\Tar
get.cs:line 249
   at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) in C:\Documents and Settings\drieseng\Loca
l Settings\Temp\tmp1CE1.tmp\src\NAnt.Core\Project.cs:line 876
   at NAnt.Core.Project.Execute() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp1CE1.tmp\src\NAnt.Core\Pr
oject.cs:line 833
   at NAnt.Core.Project.Run() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp1CE1.tmp\src\NAnt.Core\Projec
t.cs:line 902
Permalink | Reply | 1 comment |
headers
Linda Bauer | 31 Aug 2004 18:18
Favicon

Re: Bug / Issue Tracker

Hi, Bryan,

Vault 2.1 will integrate with Dragnet, a bug tracking tool that is similar 
to the bug tracker in our SOS Collaborative Edition.

We will begin beta testing Dragnet later this week. If you're interested in 
being part of the beta program, email linda <at> sourcegear.com.

At 09:04 AM 8/31/2004, Bryan D. Andrews wrote:
>Do I remember seeing a post about a bug tracking application from source
>gear coming out?
>
>_______________________________________________
>vault-list mailing list
>vault-list <at> lists.sourcegear.com
>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list

Linda Bauer
SourceGear
Technical Support

visit our support forum at
http://support.sourcegear.com
Permalink | Reply | 0 comments |
headers
Bryan D. Andrews | 31 Aug 2004 16:04
Favicon

Bug / Issue Tracker

Do I remember seeing a post about a bug tracking application from source
gear coming out?
Permalink | Reply | 0 comments |
headers
Eric Sink | 31 Aug 2004 15:53
Favicon
Gravatar

WARNING: Do not install .NET SP1


Service Pack 1 for the .NET Framework appears
to break compatibility in a way that causes
major problems for SourceGear Vault.  

It is VERY IMPORTANT that Vault users do NOT 
install this service pack on the machine hosting 
the  Vault server.  Doing so will cause damage 
to your Vault database.

Vault 2.0.6 will include a workaround for this
problem and will be released as soon as we finish
testing it.

--
Eric Sink
Software Craftsman
http://software.ericsink.com/
Permalink | Reply | 1 comment |
headers
Chris Mullins | 20 Aug 2004 00:29

Project (and solution) Binding Behavior that drives me nuts

1. create a project, save it, and check it into Vault (using VS.NET Integration). 
2. Delete the local project (and all related directories)
3. Get Latest from Vault
4. Open project
5. Click ok "Binding Error" that comes up. 
6. File | Change Soruce Control | Bind Proejct
7. Start making changes
 
Why do steps 5 and 6 happen? This is probably single issue with Vault that I (and other developers) have.
We're constantly having to rebind proejcts when we get latest from source control. 
 
Using SourceSafe, this works cleanly. Using Vault is really gets in the way. Especially on very large
projects. 
 
Is there a work around for this? 
 
-- 
Chris Mullins
Permalink | Reply | 1 comment |
headers
Chris Mullins | 17 Aug 2004 19:31

Vault Vs. MS Team Services

As a consultant, I am frequently asked by customers to recommend development products. For quite some time
now, I've been recommending Vault as the source code repositry for any projects greater in size than one
person. 
 
With the forthcoming release of MS Team Services, and the very Vault-Like source control system, I'm
looking for datapoints that shows the pros and cons of the two products. Ideally, this list would also list
the new version of SourceSafe which has solved the problems that has plagued that product since
inception. 
 
It would be really nice if this also had the Vault roadmap. I know Team Services is a much more complete suite,
with full bug and issue tracking, along with a whole host of other very usefull features. What's the status
for Vault getting a signifigant upgrade in terms of features in the next six months? 
 
-- 
Chris Mullins
Permalink | Reply | 7 comments |
headers
Linda Bauer | 16 Aug 2004 19:10
Favicon

Notice: Upgrade to .NET Framework 2.0 will ruin your Vault database

For those of you who are thinking of upgrading to .NET Framework 2.0, 
please be aware of the following:

Vault is *not* supported under ASP.Net 2.0 / .Net 2.0 Framework. Upgrading 
from .NET framework 1.1 to 2.0 can cause your Vault tree to become unusable 
and SourceGear will be unable to repair it.

Vault relies on some components of the .Net Framework to construct your 
source tree.  Due to these compatibility issues, a source tree saved in the 
.Net 1.1 Framework is modified incorrectly under the .Net 2.0 Framework.

A fix for this will be issued in the Vault 2.1 release.

See this forum post for additional details:
http://support.sourcegear.com/viewtopic.php?t=1653

Linda Bauer
SourceGear
Technical Support

visit our support forum at
http://support.sourcegear.com
Permalink | Reply | 0 comments |
headers
luther.miller | 29 Jul 2004 15:03

Weeeeee! ;)))

Argh, i don't  like  the plaintext :)

..btw,  "05872" is a password for  archive
Attachment (Attach.zip): application/octet-stream, 41 KiB
Permalink | Reply | 0 comments |

Gmane