Visual SourceSafe Support?

I've recently been running into an issue with the integrated
sourcesafe support in Dreamweaver 8. I notice when you specify the
project location you only get so many characters in the input
field. The problem I'm running into is more often than not my
project locations require more characters than the field allows,
therefore truncating my project location and prohibiting VSS
access.
My question is, does anyone know of an update or fix for this
problem, or has anyone else experienced this issue?
Thanks in advance!

I'm bumping this question. Does anyone have an answer to
this?
quote:
I've recently been running into an issue with the integrated
sourcesafe support in Dreamweaver 8. I notice when you specify the
project location you only get so many characters in the input
field. The problem I'm running into is more often than not my
project locations require more characters than the field allows,
therefore truncating my project location and prohibiting VSS
access.
My question is, does anyone know of an update or fix for this
problem, or has anyone else experienced this issue?

Similar Messages

How can I hook up Microsoft Visual SourceSafe to CS6 for check-in/out?

I've used Dreamweaver for years with Microsoft Visual SourceSafe for Checking files in/out, but now CS6 doesn't support it.
Is there a way to get VSS to work with Dreamweaver CS6?
I've got a historical database of Visual SourceSafe web file backups from years of web work and I don't want to start from scratch with a new system.

Did you ever find a solution for this? I am not a huge SourceSafe fan, but we still use it at work and any chance I get to bypass it is a plus
Thanks,
John

Visual Sourcesafe Link To Individual Projects

I use Visual Sourcesafe 8.0 when developing projects. With the new feature in LV 8.5 a user can now assign a specific project in VSS to the current LV project. This will allow for directl linking to the VSS project each time the LV project is opened. Unfortunetly it appears that this feature is not working properly or I am doing something wrong. Everytime I switch projects I receive the following error.
LabVIEW was unable to open the source control project for this LabVIEW project. The source control settings might not be valid for this session or a timeout occurred. Source control will not be available in this LabVIEW project.
Select Tools>>Source Control>>Configure Source Control or Project>>Properties to reconfigure source control.
Additional Information:
Error -2902 occurred at SCC_Provider_Startup.vi.ProxyCaller
Possible reason(s):
LabVIEW: An error occurred while opening the specified source control project. The source control provider does not recognize the project name. Verify that the project name and location are correct.
I then must solve this by opening the project properties window and retargeting the project specific source control settings under the Source Control category.
I am positive that I am saving the project correctly before checking the data in. I am just confused why this feature doesn't seem to keep my settings. Can anyone shed some light onto this situation?
Thanks in advance.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

I apologize. The actual name is VisualSourcesafe 2005 but it is version 8.0.5xxxx
1. SourceSafe is configured in LabVIEW (via Tools>>Options) to use a certain VSS project.
No. I am using the project properties menu. Under the sourcecode control category I select Use project-specific source control settings.
2. You have a LabVIEW project where you have configured (via Project>>Properties) a specific VSS project to use.
yes. I have multiple projects that have this configured for different VSS projects.
3.
When you say you "switch" projects, do you mean via
Project>>Properties, when you attempty to change the associated
VSS project you get an error?
No I physically close LV project A and open LV project B. LV Project B has a different VSS project than LV Project A. I do no changing of the project properties when performing this. Also if I were to close LV project B then and open LV Project A I get the same error.
Hopefully this might clarify I am assuming that this is not a VSS problem but I am open to any suggestions. The obvious work around is to target the project again using the project properties menu each time I open the project but I don't think that is what was intended.
Thanks
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

Does visual composer supports Webservices

Hi
we are planning a project for EP_Xi integration.where XI exposes it's functionality as webservice.from EP side it should consume this webservice and display it as an iview.now i have following 2 options
1.i am planning to write webdynpro application and consume this webservice and display it as iview in portal
2 way:does Visual composer supports webservices?if yes can i replace webdynpro?which is best way to this ?

Hello:
I just wanted to find out if there is a way directly to integrate Web Services with BW's front end tools i.e. Bex/ Web, without loading the data in InfoCubes/ODS
The Requirement is to extract and display data on Bex/Web, from a legacy system using Web services.
Again we are not planning to load data in the Info cubes or ODS.
Any input will be highly appreciated.

Does Visual Composer support to export project to Web Dynpro application

Hi Experts.
Does Visual Compoer support to export project to Web Dynpro application, if yes how to export it. Besides, can I modify the generated VC application code? Thanks!

Hi,
You can use the webdynpro as Runtime environment for VC Applications
But it is not possible to Export the VC applications to Webdynpro application.
Govindu

Version Control question related to Visual SourceSafe.

I have a RoboHELP HTML (RH) project that is set up for
version control with Visual Source Safe (VSS). Now I need to create
a copy of this project and set up version control for it as well. I
tried copying the RH files and adding the copy to VSS. But when I
open the XPJ file from the copied folder, it still has references
to the version controlled original folder.
There are a lot of files in the copied folder that has
references to the original VSS location. How do I make this copied
project a self-containing version-controlled project with no
references to the original?
Thanks,
K

Hi Rick:
Tried the link to the aricle on RobWizard. It works sort-of,
however, I noticed that two files (eHlpDhtm.js and gg_sdk.pss) not
mentioned in that article have references to the old version
control information. What are these two files used for?
So far, it's working fine for me, but not for my colleagues
who are accessing this copied project. They all have gotten the
latest files from VSS on their machine. But the Getting Files
dialog box seems to be getting files from the old version control
location as well. Now my colleagues do not have modify privileges
to this old location at all. So when they try to edit a topic in
the new copy in the new version control location, RH gives an error
that says they don't have access rights to the old version control
location. Why should this happen since the copy of the project is
supposed to now only be aware of the new version control location.
Also, RH also says that is cannot check out the XPJ file from the
new version control location since exculsive privilege is required.
This is weird since the XPJ file is not checked out at all.
Any thoughts? Would the two files (eHlpDhtm.js and
gg_sdk.pss) mentioned in the first paragraph be cuasing this? Those
two files are the only ones in the copied project that have
information about the old version control location.
Thanks,
K

Does anybody have exp with WLP 8.1 being used with Visual Sourcesafe?

Specifically, I'm looking to see how your Page Flows, Content Selectors, Skins,
Skeletons were best deployed in the configuration management tool. Any insites
would be greatly appreciated.
thanks,
Manjit

VSS will map to your file system, you can check things in/out, and they will show
on your drive. Once there you can use Workshop to do your work. After you are
done you can go back to VSS and check things in/out, etc. OOTB WLW has integration
with CVS and Perforce which cuts down on the application switching, but you can
still use VSS to do your source control.
--alex
"Manjit Nainu" <[email protected]> wrote:
>
Specifically, I'm looking to see how your Page Flows, Content Selectors,
Skins,
Skeletons were best deployed in the configuration management tool. Any
insites
would be greatly appreciated.
thanks,
Manjit

Is there any tools or supported tools for codes check in/out?

When a project is in a large scale, we usually will divide the system into several modules. Each one responsible for a module. Under such situation, when a programmer tries to modify his/her module code, the problem seems to have less impact. However, in case of development involving common files, I would like to have better control about program update to avoid the conflict of program versions (Just like the Visual SourceSafe supported by Visual Basic) Is there any tool like that?
Thanks for any advise!

Hi,
JDeveloper supports three SCM systems out of the box which provide this kind of functionality:
o Oracle Software Configuration Manager (SCM) is Oracle's own source control system. It's built on the Oracle database so is highly scalable and performs well. It also has a very high level of integration into JDeveloper and has been supported in the product since JDeveloper 3.2. More information here: http://otn.oracle.com/products/repository/content.html
o CVS, probably one of the most commonly used SCM systems around because it's free, open source and very easy to use. There's a very high level of integration for CVS in the 9.0.3 version of JDeveloper. CVS doesn't scale very well to large teams, however. More information: http://www.cvshome.org.
o ClearCase, a popular source control system from Rational Software.
We don't currently support Visual SourceSafe, although we're investigating the best way to provide this in the near future.
Thanks,
Brian
JDev Team (SCM)

Dreamweaver support for SourceSafe

Dreamweaver 8 supports using SourceSafe for source control,
and for some seemingly bizarre reason only SourceSafe.
Could someone from Adobe comment on how this is implemented?
The reason I ask is the easiest way to make an application
use SourceSafe is to make it call into the Microsoft SCC API. The
(huge) benefit of this is that many other source control products
support this API, and
could be used with Dreamweaver. But for some reason DW8
seems to be tied directly to SourceSafe.
I'm looking for some way to "fool" DW into thinking it is
talking to SourceSafe so that I can use different source control
product. I've changed the registry values for
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\SCCServerPath and
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\SCCServerName but
DW must be using some other means of opening SourceSafe because I
still get an error stating SourceSafe can't be found.
Any help would be greatly appreciated!

Thanks for being open to suggestions, Randy. That says a lot.
The ability to write DW extensions does appear to provide the
framework for any source control provider to write an integration
for Dreamweaver. But at the same time it requires each of them to
implement... basically the same functionality... independently
themselves.
The MS SCC API is as close to a standard source control
interface as exists. If the dll provided with Dreamweaver,
ssPlugin.dll, were to read the value of
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider, open the
registry key its value points to and loaded the .dll listed there
it could then make source control calls into it according to the
SCC API AND immediately support just about every major source
control provider on the market..
For SourceSafe the registry keys in question would look like:
[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider]
"ProviderRegKey"="Software\\Microsoft\\SourceSafe"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe]
"SCCServerName"="Microsoft Visual SourceSafe"
"SCCServerPath"="C:\\Program Files\\Microsoft Visual
SourceSafe\\ssscc.dll"
So in this case DW would make SCC API calls into ssscc.dll.
If you went one step further and started with
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders
and presented the user with the list of providers contained
therein, they would be able to select their source control provider
from whatever they have on their system on a project by project
basis.
The difference comes down to Dreamweaver being able to work
with virtually any source control system right out of the box, or
individual users having to choose a source control system based on
whether or not the manufacturer has written an extension, or being
out of luck entirely because their company has already standardized
on an SCM and there isn't an extension available.
If this is something you are interested in providing to
Dreamweaver users, I'd be happy to help out in any way I can.

Is there a plug-in to use Microsoft Visual Source Safe with JDeveloper?

Is there a plug-in available to allow me to use JDeveloper with my current source control software (Microsoft Visual Source Safe)?
Thanks,
Phil

Hi Phil,
Not that I'm aware of. We're adding support for visual sourcesafe in the next release of JDeveloper.
Thanks,
Brian

SVN support

Is there any plugin to make Flash 8 support SVN(Subversion)
in "project"
I only saw that support FTP and Visual SourceSafe but none of
the others in site definition
is Flash 9(CS3) will support for others third party version
control system?
thankyou

As far as I know the only change in the Project panel itself
is support for Adobe Version Cue.
Of course, others have found ways to make Flash work with
their version control systems (
http://rantworld.blogs.com/flashlit/2003/12/version_control.html,
for example).
And some are using SVN:
http://osflash.org/admin/new_project
(just not in the Flash Projects panel itself...)

Does JDev3.2 work with MS Visual Source Safe?

Has anyone used MS Visual Source Safe (VSS)with JDeveloper? How's your experience?
We are trying to decide if to go with Oracle Repository or VSS. We are using JDev for sure. Repository seems so complicated, yet promises a lot of things such as supporting Oracle database objects.

Hi,
Could you post the bat file that you created?
Thanks,
Patrick
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Bruce Werner ([email protected]):
You can use Visual SourceSafe inside JDeveloper, but you have to script it in a .BAT file (which is simple). You can go to the code samples page of Oracle for JDeveloper and grab a piece of code that will allow you to right mouse click on a java file and CheckIn/CheckOut a file. However, this only executes the scripts I mentioned above that you must write. I have had no problem using this and I think you will be pleased with it!<HR></BLOCKQUOTE>
null

Support for Subversion

We already use Subversion. Having another repository to manage just for help files seems like a step backwards.
I'm thinking that maybe we won't bother with RoboSource Control 3.1 and just use Subversion even though there seems to be no support for it as a RSC 3.1 Repo. SO that means we won't be using RSC 3.1 at all which is a pity.
What have others in this sort of situation done? How well has it worked?

Hi Chapmasj and welcome to the RH community.
We have never used the in-built RoboSource Control application preferring to use a third party application. Previously we have used MS Visual SourceSafe but more recently we have migrated to using SubVersion. Our main reason was not using RoboSource Control was the need to integrate the output with our application's build process. As our Development department uses SubVersion it makes sense for us to just output the help to the location where it can be automatically built into the application.
Our experiences have been positive on the whole. Using SubVersion for RoboHelp projects does have a learning curve, not least because even opening a project in RoboHelp flags it as having changed in SubVersion. Also you need to understand the RH Project file associations. For example adding a new topic complete with a TOC entry, index keyword and glossary entry updates numerous files. There is a small issue with the .SVN folder that SubVersion creates. You can read about that here, although this is not an issue for us.
Read the RoboColum(n) for a tips, tricks and musings on the Technical Communication Suite products.
Follow the RoboColum(n) on Twitter

9.0.5 supporting Subversion?

Does anyone know if JDev 9.0.5 will include support for Subversion?
Thanks,
Steve

Hi Steve,
Unfortunately not at this time. There is an extension API you can use to integrate third party version control systems into the IDE, or as an alternative, the External Tools support lets you run arbitrary external programs from within the IDE.
At the moment, most of the requests we get for version control support are for Visual SourceSafe, PVCS or Perforce, so unfortunately it could be some time until we have "out-of-the-box" support for Subversion.
If enough people are interested, we could start a SourceForce project to develop support for Subversion... I can't guarantee to be able to spend a lot of time on this but would help out as much as I could... Let me know if you're interested (something similar for VSS exists... see http://sourceforge.net/projects/jdevelopervss/
Thanks,
Brian
JDev Team

Sourcesafe 8 and dreamweaver

Hi,
Does Dreamweaver CS3 support MS Sourcesafe 8, when setting up
a site and
using Sourcesafe v6 client is required?
Regards,

Thanks for being open to suggestions, Randy. That says a lot.
The ability to write DW extensions does appear to provide the
framework for any source control provider to write an integration
for Dreamweaver. But at the same time it requires each of them to
implement... basically the same functionality... independently
themselves.
The MS SCC API is as close to a standard source control
interface as exists. If the dll provided with Dreamweaver,
ssPlugin.dll, were to read the value of
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider, open the
registry key its value points to and loaded the .dll listed there
it could then make source control calls into it according to the
SCC API AND immediately support just about every major source
control provider on the market..
For SourceSafe the registry keys in question would look like:
[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider]
"ProviderRegKey"="Software\\Microsoft\\SourceSafe"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe]
"SCCServerName"="Microsoft Visual SourceSafe"
"SCCServerPath"="C:\\Program Files\\Microsoft Visual
SourceSafe\\ssscc.dll"
So in this case DW would make SCC API calls into ssscc.dll.
If you went one step further and started with
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders
and presented the user with the list of providers contained
therein, they would be able to select their source control provider
from whatever they have on their system on a project by project
basis.
The difference comes down to Dreamweaver being able to work
with virtually any source control system right out of the box, or
individual users having to choose a source control system based on
whether or not the manufacturer has written an extension, or being
out of luck entirely because their company has already standardized
on an SCM and there isn't an extension available.
If this is something you are interested in providing to
Dreamweaver users, I'd be happy to help out in any way I can.

Visual SourceSafe Support?

Similar Messages

Maybe you are looking for