Transition from X5 to v7 source controlled project

We have a project running from RH X5 with it's native Source
Control server powering it.
We have now installed some RH7 clients and the next stage is
to migrate to the new version of Source Control.. But when i looked
at setting this up I discovered that RH7 doesn't seem to have
actual Source Control functionality any more, it says we need to
install an SQL server to power it..
I was not aware of this, and it is now causing me problems,
after going through the long and tortuous process of getting
approval for the RH upgrade, I now have to present another case to
get SQL server installed.
For info, I work for a major financial institute and we have
tight control on software. I know SQL server Express is free, the
cost is not the issue.. If I cannot get approval for this, what are
the options?
Meanwhile I have found a lovely workaround, installing the
Source Control element from RH5 and this allows the RH7 client to
connect to the project which is running on the old Source Control!
So at least we can connect to the project, but we've had to install
part of X5 on top of v7 which i don't see as a logical solution.
I'm hoping there is a better way (or i can get approval for
SQL server), as I need to roll this out to various other
departments who want to migrate from X5 to v7...

I wish that I had the information to tell me when it was
necessary to go from SQL Express to SQL, but alas, I don't. I did
hear somewhere that SQL Express would only handle so many
users...and no, I don't know how many that is.
You might try setting up an RSC3 DB with SQL Express and
testing it out. In my experience, RSC3 is a lot more stable than
the older version. In particular, it doesn't seem to be so prone to
freaking out over network disruptions.
G

Similar Messages

  • What does 'file was dropped from the Add to Source Control Operation" message mean

    Yesterday I upgraded to LabView 8.5.1 and moved a project from my office desktop onto the test system computer in the vault. I wanted to use the source code control integration capability with this project. I went through the process of configuring source control (I am using Serena Version Manager). All appeared to be well. LabView saw the source control software an can bring up the client. I selected all of the files in my project and selected "Add to source control". I received a message popup with a message like:
    FILENAME was dropped from the Add to Source Control Operation
    for each of the files in my project. I got the same message when I tried the operation on a single file. This did not appear to be an error or warning message, just informational. I could find no information in the help to tell me what this message really means. Any ideas?
    Mike Eaton

    Usually LabVIEW creates one dialog (with a tree-control, and an option to keep files checked out and a comment box).
    All other dialogs are from the SCC. Maybe you can configure Serena to go silent?
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • Cannot get project to open from Source Control

    When trying to open project from Source Control, it times out (at Loading Index). After numerous tries, I'll get cpd file corrupt and I follow the steps (delete file and try again); sometimes I get very strange error messages.
    Does anyone know how to fix this problem so I can open a good copy of the Source Control project on my desktop?

    Hi,
    What version/flavour of RoboHelp are you using?
    What source control client are you using? Are you using the RoboSource control on a 64 bit system? If so, you need to update RoboSource control: http://kb2.adobe.com/cps/917/cpsid_91739.html. Note that this fix is for RoboHelp 9.
    Greet,
    Willam

  • Robo HTML 9 will not open our project from Source Control after initial start.

    We have a project in version control that we have been using forever, since 2003 or so and many versions of RH.  Now that we have upgraded to 9, this project will open the first time in version control and work normally.  Once you close the project and attempt to reopen from the starter screen, it opens just great, just not in version control.  The files are still set to read only.  I have done this several times and the only way i can work on my project in version control is to act like i am opening a project from scratch, then it needs to overwrite all of my local files with the server files.  It would not be so bad but I am 3000 miles away from the server and 13 hops plus a slow firewall on the other end.  While this has never been a problem in the past it is a big problem because it takes hours for all the files to download and overwrite my local files.
    This only happens with RH9 and Version Control 3.1.  RH8 works no problem.  So, I don't know if this is a RH9 starter problem or a Source Control Problem.  Maybe I will make a similar thread in the RH area.  I'll wait to see if I get any useful hits from this one first.
    It is very strange, I had RH9 open for several days because I was afraid to close the project for this reason and yesterday I published for the month so the heat is less right now but today, it opened with no source control.  If I go to Source Control the only thing i can select is put project in source control.  That is how it got into source control after converting to RH9.
    We have another project that seems to open from version control normally but we can only save topics in HTML view.  No useful answers to that topic after a week.
    Got any ideas???
    I have tried different folder names, different paths, etc.
    Thanks,
    dv

    Ok, here is a wierd one, I used the add to version control icon in the menu bar, It already knew the path so I figured I'm the only one who has been editing these files for the past few days so I clicked add to version control.  It added it. I closed and reopeded and still had the same files checked out.  Closed, checked in all, then reopened and it is working in SourceControl.  Strange that after opening from source control and closing that you need to reopen and tell it to put the project into source control.  Obviously some flag is not getting set somewhere.  This might help others having problems reopening source control files.
    dv

  • How can I add a Website Project in a solution that should be excluded from source control?

    Using VS 2013 update 4
    I currently have a solution with a couple of Class Library Projects and Web Application Projects and all of these are bound to a source control (VS Online). Now I added an Existing Website Project in the same solution by choosing a Local IIS instance. However,
    I don't want this Website Project to be in source control.
    I have tried File > Source Control > Advanced > Change Source Control ... and then clicked on the website project and then clicked Unbind. By doing this, it seems that the project was unbound. However, as soon as I close the solution it asks me
    to save the .sln file and seems that it restored the Scc*** info in the file.
    I also tried editing the .sln file and set the SccProjectEnlistmentChoice* = 0 (of the website project, under GlobalSection) and then set the ProjectSection of the WebsiteProject to 
    SccProjectName = ""
    SccAuxPath = ""
    SccLocalPath = ""
    SccProvider = ""
    instead of "SAK". This actually worked for me but everytime I open the solution, Visual Studio alerts an error saying "Unspecified error". This is the closest I got into solving this.
    Is there a proper way of doing this? I think the proper way should be the "Unbind" method but it seems that it's not working as expected.
    Let me know of other solutions.
    Cheers!

    Hi Karlo Medallo,
    Since this issue is related to the VS Online, I am moving your thread into the
    Visual Studio Online
    Forum for dedicated support. Thanks for your understanding.
    Best Regards,
    Jack
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How to move a project in source control

    I messed up & need your advice. I put my first RH project, "core", at the root level of my VSS project:
    $
    rh_projects
       core
    Unfortunately, my "core" RH project is now a child project in a merged help system.  I also put the "parent" project at the root level, so now it looks like this in VSS:
    $
      rh_projects
         core
         parent
    ... but my VSS folder structure really should reflect my real folder structure, so that other writers can use the same structure when they open the project.
    So I want to change my VSS folder structure to this:
    $
      rh_projects
        parent
        projects
           core
    So here's my question (finally!):  what's the best way to move the core project in VSS?
    * In RH, remove the core project from source control, then put it back under source control at the new folder level, OR
    * In VSS, add the new "projects" folder structure and move the "core" folder underneath it, then open it in RH as a "new" project?
    thanks,
    Jenny

    Either way should work.
    Method 1 will ensure the source control path in the RH files points to the correct VSS location
    Method 2 will keep your change history if this is important to you. However, it is trickier to do.  Zip up a copy of your project just in case.
    Method 2 details
    If you use this method, you need to manually change the VSS path listed in the .xpj file.
    Look for something similar to the following. It may be different depending on your versions of RH and VSS. The below is from RH6 and VSS2005. '[' represents and angle bracket.
    [matchedpair]
               [name]vc::cookie[/name]
               [value]"$/Dev/Source/Documentation/MyProject", ZTZQBAAA[/value]
    [/matchedpair]
    You will need to change the [value] line: change the path beginning with $ to your project location.
    I don't think you need to change the 8 character code after the comma, but I was never quite sure what it meant. If want to be safe or things don't work, create a temporary new project and add it to VSS at the same level as your project. Copy the bit in green from the temp project and paste it into your real one. Delete the temp project.
    Also make sure you delete the .cpd file before opening the project as this sometimes remembers the old location.
    HTH,
    Amebr
    Message was edited by: Amebr
    Couldn't get colours to work so changed to words. Hopefully it's clear enough.

  • Database Project Schema Compare Source Control to target database Not working

    I am trying to use the schema compare feature of database project / TFS.  I don't understand why it is trying to DELETE a stored procedure that exists in TFS.
    The Degenerate Dimension

    Hi MM,  
    Thanks for  your post.
    If you open this solution from a local folder(not stored in TFS), and try to compare that same file, what’s the result? We need confirm this issue relate to VS Schema Compare tool or relate to TFS Source Control first.
    http://blogs.msdn.com/b/ssdt/archive/2012/03/23/schema-compare-improvements.aspx
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • The project file is not bound to source control, but the solution contains source control binding information for it.

    This may be more of a SQL Server Management Studio question, but I couldn't find a SSMS forum...
    I've got a database solution that contains several projects.  They're just to keep track of changes to stored procedures, triggers, views, etc in a few databases I maintain.  There is a problem with two of the projects though.  No matter what I do, I can't seem to get them bound to source control right.  When I open the solution, I get:
    The project file is not bound to source control, but the solution contains source control binding information for it.
    With two options, use solution binding and remove solution binding.  If I keep the solution binding, everything works fine.  But it's really annoying to have to deal with every time I open the solution.  If I remove the solution binding, the projects are now unbound again.  If I try to fix them (using the change source control or Add Selected Projects to Source Control options under the File->source control menu), I just end up in the same situation.  I've even tried deleting the projects and re-creating them from scratch, then re-adding them to VSS.  If I open the solution files in a text editor I can see the SCC tags in every project, but these two.  Since I can't manually add the tags, and Management Studio itself only seems to want to bind them the wrong way, I'm getting really frustrated.
    Can anyone point me toward a way to bind these so they work like the rest?

    However, that does not appear to be the ONLY cause of the problem.  I am a single user and only using TFS2010 and SSMS2008R2.  My issue is that I wanted a solution file for each project so that they could managed independently, and a super-solution
    file that contained all projects, so that I could perform system-wide searches and cross-checks.
    I solved the problem by:
    1. Choosing the option to use solution binding, then
    2. Adding another project to the solution.  This forced the re-write of the solution file.
    3. Adding another script to the project.  This forced the re-write of the project file.
    4. Checking in all changes.
    5. Deleting the new script and the extra project,
    6 Checking in all changes.
    This appears to have solved the problem.

  • Error when trying to add a project to Subversion source control

    When trying to add a project to source control from within the OPM 10 studio (File - Source Control - Add Project to Source Control), the following error occurs:
    "There was a problem accessing the source control system, probably due to network or contention issues. A retry is recommended."
    This has been tried with Subversion versions 1.6.2, 1.6.5 and 1.6.6, with local repositories and repositories on a Apache webserver.
    Once the project has been added to a repository, by using TortoiseSVN for example, working with source control is no problem.
    Does anyone have a clue what the problem (and a solution) might be?
    Thanks,
    Theo.

    Hi,
    Davin mentioned:
    This appears to be an issue with the source control integration. We are looking into it.I am using OPM 10.0.1.14
    The OPM help on collaborating mentions:
    Open a rulebase project from source control
    To open an existing Oracle Policy Modeling project from a source control repository:
    In Oracle Policy Modeling, select File | Source Control | Open Existing Project from Source Control. When I open the File menu I do not see the "Source Control" at all.
    Is this caused by an installation error or part of the "issue with the source control integration" ?
    Please let me know if I'm the only one experiencing this problem ....
    Thankx,
    Paul

  • Adding a Weblogic Portal from source control

    I am using Weblogic Portal 10.3.2 and Eclipse 3.5.0. I can successfully create the EAR and portal projects, deploy them, etc. No problem. If I try to copy the projects to another computer or check them into a source control system and check them out on another computer I get the
    "Portal Application Services web application should be associated with a Portal Application Services EAR for proper deployment"
    and
    "A WebLogic Portal web application project should be added as a J2EE module to a WebLogic Portal EAR project for proper deployment" error messages.
    I did a directory comparison between a portal project that does work and one that doesn't; they are identical. The only thing I can think of is the ".metadata" directory is different, but this is huge, 1000s of files, over 100 MB.
    Has anyone seen this? Any idea of what the problem may be?

    Hi
    The reason for this error is most probably the portalEAR project is not associated wtih the portalWeb project. For any portal application, we must have a portalEAR and a portalWeb project and portalWeb project should be associated with that portalEAR project.
    For your existing and original working portal application, check the .project file in textpad located at: ...\user_projects\workspaces\Your_Workspace\yourPortalEAR\.project. The top contents will be like this:
    <name>myPortalEAR</name>
    <comment></comment>
    <projects>
         <project>myPortalWeb</project>
    </projects>Once you checked out and added them to the new machine and new workspace, check the same file. If not, after importing from CVS or source control, open both portalEAR and portalWAR in Workshop IDE. Select your portalEAR, right click mouse -> Select Properties -> From properties window on left side, select J2EE Module Dependencies and on right side check the check box corresponding to the portalWeb module. NOW you may need to do this everytime.
    Usually this is what I do, if I want other team members to get my portalApplication (EAR, WAR and DataSync project) or to check into source control. I DO NOT check-in or Export individual modules. Instead I Export them as single Archive File.
    From Workshop IDE, on left side right click -> Export -> From Export Window, Expand General -> Archive File -> Click on Next. In this window, select all the 3 projects on top left window ie. EAR, WAR and DataSync (if you have one). Then give a valid filename for this ZIP file something like myPortalEARZip.zip etc. Then click on Finish. This will create a big single ZIP file. NOW you can checkin this ZIP file or give to other team members.
    Now other team members will open Workshop IDE. Left side rigjht click mouse, select Import -> From Import Window, Expand General -> Existing Projects Into Workspace -> Click Next -> Select the radio button named Select Archive File and hit Browse and choose the above .zip file. It should list out the exising projects from this zip file. NOW mostly you may have to delete the exising same projects from this Workspace before you Import. Then follow the steps and you should get all the projects into your workspace. Do clean build etc.
    There may be some other simpler approach, but usually I follow the above proceedure. If you want to continue your existing procedure, then manually link portalEAR with portalWeb project.
    Thanks
    Ravi Jegga

  • 3 questions - Source control vs. sub-projects

    Hi -
    I have 3 related questions:
    1.) Seems like I remember a warning from a long time ago
    (older versions) about having to check out the entire project -
    because the user needs to access the .mpj/.xpj file. How does the
    new RoboSource Control 6 handle checking out the project file?
    2.) Also - Is it better to use sub-projects (merged projects)
    or Source Control to support multiple users?
    I believe one "con" to using merged projects is that you have
    to manually deal with consolidating context IDs... Can anyone give
    me some other pros and cons for each method?
    3.) If I go with Source Control as the method for handling
    multiple users - combining all of my topics into one project - I'm
    concerned about the size of the project. I've encountered seriously
    long compile times and corruption in past versions. Can anybody
    provide real-world numbers for project size and compile time in
    RoboHelp 6?
    Thank you.

    quote:
    Originally posted by:
    OE3-chick
    Hi-
    1.) Hmm.... so I think this means the the .xpj file would
    still be accessed directly from a file share. So, if we worked
    together and I opened the .xpj file to work on the project -
    wouldn't it give you a warning that the file is already in use when
    you go to open it and also work on the project? Can two people open
    the same .xpj file now?
    Oops, seemingly my fingers started typing the usual
    answer before the brain achieved operating condition. The XPJ
    contains no local stuff and can and should be committed to the
    database. I was referring to CPD, PSS, and LDB.
    quote:
    Originally posted by:
    OE3-chick
    Regarding 2.) and 3.) Oop - I'm actually referring to authors
    (users of the RoboHelp application). I was told that creating
    seperate projects would allow multiple authors to use RoboHelp -
    then they would be merged into a single project for the end
    customer. So, my concern is about which method (
    sub-projects/merged projects or Source Control) is better for
    supporting multiple authors.
    RoboSource Control is set up in such a way that multiple
    authors can concurrently work at the same project. As soon as one
    author manipulates a file from the project, this file is locked for
    the other users. As long as different author ditribute the work on
    the topics they can work without interferences. Exempt from this
    optimistic description are the central files valif for the whole
    project: HHC (table of contents), H and ALI (context sensitive
    help), GLO (glossary), and BRS (browse sequences). the same is true
    for the HHK (index), as long as you set up the project for using
    this HHK-file.
    So if you can teach your authors to concentrate on their
    topics (and index entries) only in their work, and handle the other
    stuff centrally, no one will ever notice that she is not the only
    one working on the project. With up to five or six authors even the
    conflicts are not so bad. Just ask the other who has locked, say,
    the HHC to check it in and you can immediately work on the table of
    contents yourself.
    The other method using separate projects and merging the
    stuff at run-time avoids these problems, but at a cost. Every
    author can work on his (sub-) project to her heart's delight, but
    getting the stuff together to form a seamless unit which looks to
    the user like one help system only, takes some work. If users
    should be able to open the help system via a context sensitive call
    and the help should look a unified whole (all the help within one
    window, index and TOC seamlessly merged, navigation through links
    without errors), you'll have to fiddle around a bit.
    quote:
    Originally posted by:
    OE3-chick
    -- Is it better to use sub-projects (merged projects) or
    Source Control to support multiple authors?
    I believe one "con" to using merged projects is that you have
    to manually deal with consolidating context IDs... Can anyone give
    me some other pros and cons for each method?
    If your programmers open the same help file for every help
    call, you'll indeed have to manipulate the context IDs in a way
    that RoboHelp does not support in its interface. Where a 'usual'
    mapping reads:
    CONTEXT_STRING=PATH/TO/MY_TOPIC.HTM
    you'll have to write something like:
    CONTEXT_STRING=MS-ITS::MAIN_HELP_FILE.CHM::/SPECIAL_HELP_FILE.CHM::/PATH/TO/MY_TOPIC.HTM
    For each topic in one of the slave help files you'll have to
    manually enter such a line into the MAP.ALI of the main project.
    This works remarkably well, unless a user tries to open a
    slave help by doubleclicking it in the Windows Exporer; he will get
    an error message instead of a TOC.
    quote:
    Originally posted by:
    OE3-chick
    -- If I go with Source Control as the method for handling
    multiple authorss - combining all of my topics into one project -
    I'm concerned about the size of the project. I've encountered
    seriously long compile times and corruption in past versions. Can
    anybody provide real-world numbers for project size and compile
    time in RoboHelp 6?
    -Thank you.
    Nope, as we are running X5 I can't answer this. But anyway, a
    2,000 topic project takes some two minutes as far as compilation
    goes; I wouldn't worry too much about this.
    Regards
    ---Dirk Bock

  • Steps to export B2B Project and Source Control.

    Hi,
    I need steps to export a B2B project for source controlling it and deploying the code to higher environments.
    Right now the coding is done in DEV , We want to push it to TEST.
    Thanks for all the help.
    Regards,
    Sid.

    Documents which we have created newly will also be exported, provided it is part of the agreement.
    another answer
    First time all "export-import". Every change - incremental export and import

  • Is there a proven method of source control that would allow multiple authors to work on the same RoboHelp v11 project? Any advice would be appreciated.

    I was wondering which means of source control has proved the easiest to set up and live with for working concurrently on a RoboHelp project. Ideally, we would like to use Subversion, but would also consider Sharepoint, or other recommended solutions. Any experience you could share would be much appreciated.

    You could do a lot worse than look through the discussions over in the Source Control forum. Personally I use SVN although not integrated through the RoboHelp UI. There are others that do though. You'll find there are a selections of users using all sorts of source control apps with RH. Others not mentioned so far include Perforce, Team Foundation Server. It should just be a case of making your choice and then testing it to ensure it meets your needs.

  • Opened a SSAS project through connecting to analysis service server.. now need to put into source control

    hi there:
      I've connected to a SSAS project using connecting to analysis service server ... After a few modifications, I'd like to save it under a different name and eventually get put into the source control...
     Can someone tell me how to do that?
    thanks
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Hi Cat_ca,
    In your scenario, you can create a
    Import Analysis Services 2008 Database project to import the AS database to the project, and then change the database name following the steps below.
    Right-click the project and select Properties.
    Go to deployment option on the left pane.
    Change the Database name.
    Then deploy the project to Analysis Services server. The screenshot below are for your reference.
    Regards,
    Charlie Liao
    If you have any feedback on our support, please click
    here.
    Charlie Liao
    TechNet Community Support

  • Project management + Source Control

    we are using labview 8.5 and not well known source control in a team environment. I'm not sure if it is the souce control that I'm using or other searsons, but I had so much trouble using those combination. I want to know what others thought about project management and/or source control in general.
    Thanks,
     - Jimmy
    - Jimmy

    Hi!
       Actually, I've never merged, since I'm the only LabView guy on our development team
       I absolutely agree with the fact that SVN is a good tool, but I should confess that I didn't spend much time in evaluating many other tools (never tried MS tools), for this I rely on my colleagues' opinion.
       I can report that SVN is being used in a graphic studio for pictures versioning of course, they don't need to merge images   There's virtually no limit in SVN use...
    graziano

Maybe you are looking for