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

Similar Messages

Version Control Questions

Hi everyone,
Can somebody please tell me how to create a copy of a project
that can be opened, edited, etc. without affecting the project we
have in Visual SourceSafe? We are trying to create printed
documentation from our CHM files, and rather than playing around
with our working project, we want to test a copy first. I copied
the project in Explorer, opened it and got a dialog box regarding
SourceSafe options. We went to File -> Remove from Version
Control, and that removed the working project from SourceSafe.
All I want is a copy of the project to play around with until
we get it to look like we want, and then make the changes in the
working project.

I'm having version control woes as well. I'm working with a
CHM project that I created with RH6 and had under Visual Source
Safe control, then reopened today (after a year) with RH 7. Of
course it took FOREVER to check out and convert to RH 7 and RH
crashed in the middle during the conversion so I had to reopen,
recheck out files, etc. Ever since, I've been running into a lot of
odd things, like files that it won't check in because (according to
VSS), they are currently checked out twice, files that remain
checked out in VSS even after I do a "Check In All" from RoboHelp,
graphics that I've added to topics that aren't getting added to the
project OR VSS, and while they appear in Preview, don't appear in
compiled output. Suffice it to say: There are definite "issues"
going on between RH and VSS.
I'm considering removing the entire project from source
control (from within RH, of course), then going into VSS and doing
an "Undo Checkout" for all the files that RH is not checking in for
some reason, then deleting all project files in VSS (with "Destroy
Permanently" but keep local copy settings), and then REadding the
project to VSS from within RH.
Does this sound like a reasonable approach? I don't need to
keep any history on these files because they have not been
published yet. But I do need to get on with this project and I
think perhaps because of the RoboHelp upgrade to 7, that I need to
somehow get a fresh start in source control...?
Advice appreciated!
kc

Development backup and version control questions

Two question I want to ask as an Oracle XE beginner:
1.How to backup my work (database objects and application pages) each day?
2.What is the best practice for version control for the Oracle XE development projects? Does anyone use CVS?
Thank you.

Two question I want to ask as an Oracle XE beginner:
1.How to backup my work (database objects and
application pages) each day?Take a look at the backup script in the product directory.
C.

Version Control for Application Express

Hi all,
We are using Application Express (HTML-DB) 2.0 with Oracle 10g Release 2. We have developed a number of pages within our application (basically sales reporting). We are starting to get ready move these pages to a test and production environment.
Before we move to a production environment we need to implement a version control and migration (development -> test -> production) system. I have read various posts about importing and exporting pages and applications that have been very informational. However, I am still not clear on certain areas, any help/information on the below questions/comments would be helpful.
1.     How are other people implementing version control? For some of our other environments (for example, PeopleSoft-SQR) we use Visual Source Safe. Can we use this along with Application Express or is there a way to keep track of versions within Application Express it self?
2.     I see you can view a pages history at Home>Application Builder>Application 107>Page Definition>History. Is there a way to view the differences between the pages or to revert back to an older page?
3.     I know you can export a single page but that leaves shared components behind that might leave the complex page in a non-working state if imported and installed in the production application. Is there a way export and import shared components, for example LOVs?
These are a few of the questions I havebut I thought it would be a good place to start.
Here are a couple of links that have given me some information related to the topic.
Synonyms
http://htmldb.oracle.com/i/doc/mvl_manage002.htm#sthref1206#BABFBBEE (I believe this is for HTML-DE Version 1.5I did look in the same area for 2.0)
Version Control
How do people version control HTML DB applications?
I would be interested in hearing your thoughts and ideas on this topic.
Thanks,
Stuff

Stuff - this is also something we've been grappling with.
Did you see the excellent tip about using Web server (or PL/SQL) redirects to point to the current app? The idea is that you copy the current prod app, work on the copy and then update the redirect to point to the new app when it's released and make the old app unavailable.
This is quite brilliant in its simplicity, and has the added benefit of leaving the old app intact for bug fixes and re-releases, (or even rollback) if necessary. However, the problem with it, and the reason it's no good for our purposes, is because it sits on top of the same schema, so if the version control applies to objects in the database (i.e. the schema itself or packages etc.), then you're snookered (as far as I understand it anyway).
In a previous project, our suppliers used VSS and versioned code at the app and function/procedure/package level - I'd love to know if anyone has a robust scheme for versioning at page level.
I suspect History is an audit trail rather than versioning - I can't imagine that all the objects in all their respective states are being persisted for anything other than 'undo' purposes.
Versioning at page level seems to be problematic but it can be done, provided that the shared components are sufficiently consistent. The trick is to edit the security group ID, but the usual caveats apply.
What seems problematic to us is how to create a build out of components at different versions, like you might in a conventionally-packaged exe. I think we might end up checking in (or just saving in the file system) consistent versions at app and package level (having developed and tested in a separate schema or instance), and doing an overwrite of the prod app plus running a DDL script for package/function/procedure updates with schema deltas and other things like image uploads applied manually at cutover.
I suspect that once I delve a bit deeper into where all these objects are stored, there will be more potential for scripting, but I'm not entirely confident that this will, reliably, give us entirely what we had in Pre-Prod. Another problem I've found with this approach is that packages don't get consistently replaced.
It may simply be that we're applying waterfall concepts to what is really a RAD tool, but in any case this is my first Web-enabled development so I've been at sea with everything from design methodology to version control.
Like you, I would be really interested to hear of other suggestions.
Regards,
John.

Version Control for OSB Proxy/Business Services ?

Dear all
I've used the browser-based osb console to expose a legacy web-service as follows :
1. Create a Session
2. Create a BusinessService based on the legacy web-service WSDL
3. Create a ProxyService based on the BusinessService WSDL
4. Activate the Session
I now have two further questions :
1. How do we version control the OSB "code" ? (we use Subversion for other code)
2. How do we implement it in other environments (TEST, PROD, etc.)
Thanks,
Peter.

>
Are there other reasons why you say it's not the most ideal way of development ?
>
Versioning binary files is always a pain. You can't compare them, you can't merge them ... Another point, if you put your jar archive with OSB artifacts under version control, you will most probably face issue related to end of line styles (mac, unix, windows).
However, the most important point is usability. I want to version .proxy and .biz services to see right in IDE that I changed something and I should check that in for the others. I don't want to risk that I forget something. And I also want to see what other users committed, what sources they work on ... You loose all of that by versioning jar file. I would never go this way.

OWB Process Flow - How is the best version control tool ??

HI all,
I just start work with OWB and I have a question to know how is the best way to do something.
Imagine the scenario below:
If I have 2 or more requests for example:
Request 1: Create a Dimension City.
Request 2: Create a Dimension Products.
I Have ONE process flow and i need put my changes inside. This is my problem.
In my scenario I don't know what Request goes to Prod First.
If I put the Request 1 and Request 2 in my PROCESS FLOW, maybe I need change is someone decide change MY REQUEST PRIORITY.
There is something in OWB to "control the version or changes" ?? For a mapping I export the MDL and commit on SVN, but I dont know haw can i do with the process flow.
Something to agree multiples peoples work in different mappings and a SAME PROCESS FLOW ??
What is best way to work with process flow and version control.
What are the best practices when it comes to version control?
Thanks.

Amit,
Are you really doing this in 10.1.3.x and not 11g?
At any rate, I don't see how #2 and #3 relate whatsoever to your choice of a version control system. OK, maybe in #2 if there is some "maintenance" activity to be done against the version control server. Subversion is the open source alternative that you listed there and is pretty commonly used. If your company is already using one of the mentioned tools, why change? About the only thing I'd mention is to advise you NOT to use CVS for well documented reasons (JDev does support it) - if you would have picked CVS otherwise, choose Subversion. As far as question #1 - I've only used Subversion (well, I did use CVS for a while) with JDeveloper, so I can say it was "effective enough for me." In 10.1.3.x, I also used the external svn tools for doing lots of things like merging and so forth; in 11g, the support is much much better.
Best,
John

How to add Stored Procedures to Version Control

My system mainly relies on stored procedures and I recently noticed I don’t have the version control for my database.
So, my question is: How can I add stored procedures to version control?

Once you have a database in a SQL Server Database Project, integrating to Source control is the same as any Visual Studio project. First you configure Visual Studio to use TFS for Version Control:
Then you can configure a workspace connected to a TFS server and add your projects to source control.
See, eg
Walkthrough: Exploring Team Foundation Version Control
David
David http://blogs.msdn.com/b/dbrowne/

Report Builder RDF, XML, REP and Version Control

I'm looking to convert our existing RDF reports to XML format to better support version control and have a few questions.
- Are there any issues with converting these RDF files to XML and developing them going forward?
- When it's time to deploy to the server we'll convert them to RDF or REP. Any issues?
- This question was asked before, [Thread: Oracle Reports Builder - RDF vs XML|https://forums.oracle.com/forums/thread.jspa?threadID=721959], but that was over 3 years ago. Have the issues been resolved?
- Is anyone currently following the workflow I've outlined with success?
Couple of links of interest regarding this topic.
[Tuning Oracle Reports - 20.5.1 Paper Layout|http://download.oracle.com/docs/html/B14048_02/pbr_tune.htm#i1007252]
[Running Report Requests - 13.3 Deploying Your Reports|http://download.oracle.com/docs/html/B14048_02/pbr_run.htm#i1008764]
My Oracle Report Builder Version Info (Help -> About)
Report Builder 10.1.2.0.2
ORACLE Server Release 10.1.0.4.2
Oracle Procedure Builder 10.1.2.0.2
Oracle ORACLE PL/SQL V10.1.0.4.2 - Production
Oracle CORE 10.1.0.4.0 Production
Oracle Tools Integration Services 10.1.2.0.2
Oracle Tools Common Area 10.1.2.0.2
Oracle Toolkit 2 for Windows 32-bit platforms 10.1.2.0.2
Resource Object Store 10.1.2.0.2
Oracle Help 10.1.2.0.2
Oracle Sqlmgr 10.1.2.0.2
Oracle Query Builder 10.1.2.0.2 - Production
PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production)
Oracle ZRC 10.1.2.0.2
Oracle XML Developers Kit 10.1.0.4.2 - Production
Oracle Virtual Graphics System 10.1.2.0.2
Oracle Image 10.1.2.0.2
Oracle Multimedia Widget 10.1.2.0.2
Oracle Tools GUI Utilities 10.1.2.0.2
Edited by: 896352 on Nov 9, 2011 2:35 PM

Hi Michael,
Per my understanding that you want to find a solution for version control when you design the report using the Report Builder 3.0, right?
As you know that Report Builder is a tool which can only work on one single file instead of a project , so the current version of Report Builder doesn't have these capabilities. You can submit a feature request about it on the Microsoft UserVoice site
here:
http://visualstudio.uservoice.com/forums/121579-visual-studio/category/53187-sql-bi-tools-srs-ssis-ssas-
Generally, visual Studio Team System and Visual Source Safe integrate with the Visual Studio/BIDS shell and third-party source control solutions like SVN managed from the file system play well with version control. So I would suggest you to consider use
them instead.
In conclusion, one possible workaround for you is that you can save all .rdl files in third part tool’s(TFS) workspace folder for version control purpose (check in, check out with the Windows Shell Extension), and you can use Report Builder to edit these
report files. Then use Report Builder to deploy the .rdl file to Report Server.
More details information about the version control for your reference:
https://sqlserverbiblog.wordpress.com/tag/ssrs-version-control/
Similar thread for your reference:
https://social.msdn.microsoft.com/Forums/en-US/939b3a90-067d-4593-b456-76533c9d60ce/sync-ssrs-visual-studio-project-with-ssrs-server-alm?forum=sqlreportingservices
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/1ad0db30-7fd8-4007-9731-ec8f2f44605f/report-format-rdl-version-control?forum=sqlreportingservices
If you still have any question, please feel free to ask.
Regards
Vicky Liu

Source Configuration Management / Version Control

I was wondering what the Forte raving masses out there are doing about Source
Configuration Management and Version Control type of issues?
Have you been able to implement or "skunk work" a packaged product with your
Forte development environment?
Our shop consists of WindowsNT Forte developers coding for predominantly
Windows95 clients and a HP UNIX Central Server. At this time we currently use a
home grown "system" to handle Source Configuration Management and Version
Control issues. We are now looking to see if there is a better way to do this.
We've identified several Industry Standard packages (SCCS, CVS, Microsoft
SourceSafe etc.) and still haven't found anything very useful.
What I am seeing is that all of the packages so far have direct hooks in C++,
Visual Basic etc.
I have yet to see something with Forte hooks.
Kelsey PetrychynSaskTel Forte Technical Analyst
ITM - Technology Solutions - Distributed Computing (OTC)
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:[email protected]
Quality is not job 1. It is the only job!
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Kindly specify the email address to apply to for the mentioned job

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

Version controlling tool

Brian,
We are going to use Oracle 9i database & 9i AS & JDeveloper 10g as tool for our web development. We have been using SourceSafe as version controlling tool successfully, but could not decide what we should adopt for the integration.
I do know that Oracle is not planning further development for Oracle SCM and as such recommends all new development with JDeveloper makes use of open source tools such as CVS. JDeveloper offers different choices for your configuration and team development environment. You can continue to use Oracle SCM with the JDeveloper extension or you can use open source tools such as CVS.
My question is
You said that you can confirm that SourceSafe will definitely be supported in the next release. (Apr 19, 2004 9:31 AM Subversion Source Control). Has it been released?
If not, what is your advise on tool to use for our development team?
Thanks in advance,
YingShi

Hello Moshi,
Personally I never understood how the integrated version control system of
CVI works, but SVN (and TortoiseSVN) works fine with CVI projects.
UIR files are treated as binary, as they should be, and that's about all.
You could put the .tui file under version control instead, but I don't think
it's worth the bother.
Guillaume Dargaud
http://www.gdargaud.net/

Version control for PL/SQL. Which is the best approach?

We are developing a quite complex system which involves several
pl/sql packages, some triggers and stored procedure. We have a
version control system (StarTeam) in which we can store the
history of each change at our pl/sql code.
The problem is: which is, in your opinion, the best way to "mark"
a version in pl/sql? For example I putted a costant in a package
interface named "Version=1" which I increment for each new
release; but what about trigger and stored procedure? I need a
system, as simple as possible, which allows a customer to query
the database and tell us "which version" of the overall system
(package+trigger+proc) he/she has.
Thanks in advance
Nicola Farina

Most version control systems have special keywords that can be
inserted into the text. In Visual SourceSafe the following can
be added as part of your packages, triggers etc.
-- $Logfile: /LMES+/LMES_db/packages/batch.body $
-- $Revision: 4 $
-- $Date: 01-09-03 12:33 $
The benefit of this is that the version control system maintains
the file name, version number, date etc. You do not have to
remember to update them!
Then you can create a procedure to retrieve the information from
all_source/user_source.
Bo Pedersen

Version Control for Oracle 8i

Could anyone please suggest a version control system to use with Oracle 8i?

You can use MS Visual Sourcesafe on windows. RCS or sccs on unix/linux.
But isn't the Change Management Pack already included in Oracle8i's OEM? When it is, you can use that to generate base versions, templates and administer versions.

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

OpenScript: Which files to put under Version Control?

Hi,
According to JB's description of [how to enable Subversion|https://forums.oracle.com/forums/thread.jspa?messageID=10677356] for OpenScript, I have now an active version control.
The next question is now: which files I should put under version control? Obviously, the script.java is a good decision, but there are many more, such as java, properties, but also specific folders like "recorded data" and "results" folder.
Which once I should put under version control, any recommendation?
Thanks a lot in advance!
Volker

Thanks for your replies,
it's nice to know that I was going the right way.. :)
But how do you handle these little bugs, that I mentioned in my first message? Do you check-out all files in the project before work? Or they are TeamSystem - specific?
Best wishes, Serg.

Version Control question related to Visual SourceSafe.

Similar Messages

Maybe you are looking for