You will want to add 'use strict;' to the top of your code and turn on warnings using the -w command line flag or 'use warnings;'. This will help you pinpoint many syntactical and other errors. See here and here for why.
You're pretty much there with your existing code, a few slight adjustments should make it work:
# the object name is actually SourceSafe.0
my $vss = Win32::OLE->new('SourceSafe.0');
# you must include the path and filename
# of the vss ini file you want, e.g.
# c:\data\sourcesafe\dev\srcsafe.ini
$vss->Open($srcsafe_ini, $user, $pwd);
# error checking
if (Win32::OLE->LastError() != 0)
{
print 'Error: ', Win32::OLE->LastError();
}
If you're using the Activestate distribution, you should be able to use the HTML OLE Browser to see properties and methods available.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|