Visual Source Safe keeps checking out my .cs file associated with a report

Hello there.
I am new in this community and I need some help. I am part of a team that works with Crystal Reports under .NET framework and we are using Ms Visual Source Safe. Any time we open a solution (.sln file) all .cs files associated  with a Crystal report are checked out. This, of course, drives all of us crazy. If I try to delete the .cs file, it is added automatically. And we could not find any solution to this problem.
I compared the 2 .cs files (before and after check out) and the indeed differ. The namespace , to be more specific is different.
I believe the problem is that we are using a separate project that contains the report files and then those .rpt files are added as links to the main project.
So ... my question is... is there anyway I can tell Sourcesafe or Crystal report or any other program, application or person to stop checking out my .cs files or stop modifying them?
Thank you.

Hello  Don.
Thank you for your answer.
It seems I have SP1 already installed. I am referencing the following files with versions in my report project:
CrystalDecisions.CrystalReports.Engine v12.0.2000.0
CrystalDecisions.Enterprise.Framework v12.0.1100.0
CrystalDecisions.Enterprise.InfoStore v12.0.1100.0
CrystalDecisions.ReportSource v12.0.2000.0
I personally believe that the problem is with the link files.
To be more exact, I have several projects (csproj) that handle all reports and report loading. I also have several applications that refer these projects (not all in the same time). Because all .rpt files are loaded at runtime, I made these files Embedded resources and I created a folder in the main projects named Reports where I added all .rpt files as links.
When I open main application A solution, all .cs files associated with the .rpt files are checked out (the namespace is modified to A).
When I open main application B solution, all .cs files associated with the .rpt files are checked out (the namespace is modified to B).
And so on.
And since we are a team of several developers working with all main applications, this is rather annoying.
I hope this presents my situation a little more clear.
Any ideas?
Thanks again

Similar Messages

  • Visual Source Safe VI checked out but cannot edit

    I am using LabView 7.1 and Visual Source Safe (VSS). Previously, I have created several VI's and used VSS to manage them without a problem. I received a VI (and sub VIs) from another company location -- I copied them into my local directory -- and copied them from there into VSS.
    I then check out the files (using VSS or using LabView|Tools|SourceCodeControl ... I have tried both) but I am not allowed to edit the VI -- all I get is the "operate" cursor. VSS shows the VI as "checked out". My local directory shows that the VI file does not have the "R" attribute (read only) set. So I should be able to edit the VI, but I cannot. ????
    If I try to use LabView|Tools|SourceCodeControl to check the file out again ... I get an error, stating that I already have the file checked out, and I cannot check it out again. LabView seems to "know" that I have the file checked out, so what might be preventing me from editing it? [I tried different settings in the tool palette, but regardless of what is set, I only see the "operate" cursor when I try to work on the VI.]
    I am relatively new to LabView, and have only been using it with VSS for a couple of months now . . . . so it could easily be something simple that I am overlooking...

    Hi Rich,
    I'm happy that your issue was solved.
    Now, for the suggestion about placing the "Change to Edit/Run Mode" in the "Edit" menu - that DOES sound like an intuitive choice. However, I can also see the logic in having the menu item under the "Operate" menu - for choosing how to operate your front panel and block diagram.
    I would recommend you (and anyone else with good ideas) to submit your Product Suggestions through the 'feedback' link on www.ni.com/contact. Our R&D team will then look into the possibilities of implementing the feature in future versions of LabVIEW.
    We appreciate your ideas, thanks.
    - Philip Courtois, Thinkbot Solutions

  • CR files are automatically checked out (with Visual Source Safe 2005)

    Dear CR Support,
    i have a strange problem. Every time i open my solution in V.S. 2008 (V.B.) all my CR files are checked out automatically.
    I must do "Undo Check Out" every time.
    I Use:
    Visual Basic 2008
    Crystal Reports 2008
    Visual Source Safe 2005
    For any extra information, please let me know.
    Thank you in advance.
    Best Regards,
    Navarino Technology Department.

    Dear Don hello,
    sorry for that.
    I have made some tests and i notice the followings:
    I'm working in a CR file in design mode. I make the changes that i want, i click save and then "Check In" in order the changes to be saved in VSS. If i Don't "close" the CR File (the open tab of Visual Studio) the CR file stays "Open" in design mode. If i right click over the tab of the CR and click "close", the CR closes. This is what i mean "Open" and "Closed" file.
    - When i open the solution with the crystal reports files open (design window open), the files are checked out automatically.
    - When i open the solution with closed the reports, i have no problem. But if i try to open (in design mode) the crystal reports files, the report is checked out automatically (this is not happening to all reports).
    I will try to reinstall the SP2 again.
    Is there any newer Patch after the SP2, in order to install it?
    Thank you for your reply.
    Best regards,
    Navarino Technology Department

  • RH8 with Visual Source Safe

    My client is looking to pl
    ace our RH8 project documentation on a visual source safe server. The documentation consists of restricted information.I've read some of the posts on RH with VSS but wonder how it's working today with RH8.

    Hi Kutra
    I'd like to preface that it's great RoboHelp has some ability to interface directly with source control systems.
    However, having said that, I'd also like to say that I'm a pretty staunch advocate of the "KISS" approach with things. (KISS=Keep It Surprisingly Simple) What you are stating sort of underscores the reasoning for my approach.
    By isolating the Source Control component and working with it separately, you typically don't encounter oddities such as the files disappearing from the FPJ. My own preferred way of working with source control is to open the source control interface, check out the project, open RoboHelp and make edits, close RoboHelp and the project, then use the source control interface to check the project back in.
    Call me crazy if you like but I've never encountered an issue with working that way. And when things go wrong (as they often do) you don't have that added layer of uncertainty wondering things like "is RoboHelp possibly causing the issue here by taking actions I cannot see?".
    Cheers... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7, 8 or 9 within the day!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

  • Correct use of LabVIEW 8 with Visual Source Safe

    I have LabVIEW 8.0 and Microsoft Visual Source Safe 6 (VSS) installed and was looking for help with the correct way to integrate the two environments.  This will be used in a team environment and code modules will be shared between team members.  I have used and understand the new project manager with it's virtual directory structure.  I have also used and understand VSS and its abilities to share and branch vis or project folders. 
    When you share an item in VSS, the vi is available for use in both projects and physically resides in both projects within your working directory.  If I were just using VSS, this is the method I would use (and what is recommended in the VSS documentation).  This way an entire project contains all the files and can be retrieved all at once. 
    When you use the LabVIEW 8 project manager, it appears that the intent is to only have the code in one location and share it through virtual folders.  This makes sense and works fine until LabVIEW 8 and VSS are both used.  LabVIEW 8 can handle check in/out and adding files to VSS.  A LabVIEW project can even use vis that belong to other LabVIEW projects and other VSS projects.
    My concern with all this is what happens when a team member wants to bring down code to their working directory or rebuilding my own working directory.  LabVIEW's project manager does not appear to provide a direct view to the VSS database.  I can go into VSS and pull down a LabVIEW project file (lvproj file only) and open it up.  All appears to be fine and all VSS information is intact.  What is not there is any indication of which files actually exist in my working directory or any way to perform a "bulk" retrieval of all the files required in my project.  If all the files reside in a virtual directory, I don't even know where to go get them from.  One solution could be to follow the VSS style and ensure everything is native to a project or at least shared with a project (within VSS).  This may be cumbersome and would not follow the LabVIEW project philosophy.  I may also miss something since LabVIEW "remembers" where stuff is for you.  Following the LabVIEW project method could make it difficult to bring a project back to life and also has the potential to leave some vis out of source code control (sub vis don't have to belong to a LabVIEW project).
    Does anyone have thoughts on this subject?  What is the most efficient way to ensure that all project items are in source code control and that all projects are retrievable and functional?
    Thanks,
    Greg Cloutier

    Greg,
    I'm not a VSS guru but I do know that currently there is no automatic functionality for checking in\out a project and all associated files from LabVIEW.
    As for finding the location of the vis that have been checked out, LabVIEW can display the full path of a vi from the project explorer. If you right click on a vi and then select properties, the General category will show the full path.
    There are a number of papers that do relate to using SCC with LabVIEW 8. check out Using Source Control Software with LabVIEW and that will link you to other documents as well.
    Chris C
    Applications Engineering
    National Instruments
    Chris Cilino
    National Instruments
    LabVIEW Product Marketing Manager
    Certified LabVIEW Architect

  • Visual Source Safe and RoboHelp for HTML

    Do you ever successfully use Visual Source Safe for RoboHelp
    for HTML? I got error when I checked out the file, looks like file
    format in RoboHelp is not supported in Visual Source Safe. Can
    somebody share the experience? Thanks a lot!

    Hey, Cathy!
    The RoboSource Control in X5 was "adequate" in its day. But
    remember, that was nearly 4 years ago
    The problem was that the "free" Access database was not
    really robust enough and to really make use of it, you need to use
    MS SQL Server, which is expensive.
    That was then. This is now. The RoboSource Control 3 that
    comes with RoboHelp 6 is WAY more better
    This is because, it allows you to use a free version of MS
    SQL Server Express for a much more robust database.
    So my advice would be to upgrade to RoboHelp 6 for sure. It's
    not just hype. If for some reason you can't upgrade, then you might
    be able to get away with the Access Database given that there are
    only two of you. Since you already have it, you could create a
    little test bed project and try it out. (I have a suggestion for
    how to do that in my article. See link below)
    For the lowdown on RoboSource Control 3 see this Matthew
    Ellison's fine article
    Getting
    started with RoboSource Control 3 in RoboHelp 6
    If you're interested in the "old" RoboSource Control that
    comes with X5, you can check out my article to get you started.
    Sharing
    One RoboHelp Project Among Multiple Authors
    Thanx,
    john

  • VISUAL SOURCE SAFE

    Im trying to use Visual Source safe as a source control with Oracle Forms. Can anyone tell me what registry entries , ect. I have to change in order to get forms to work with it.
    Thanks

    I don't think you can do it with VSS.
    Those entry are currently for Oracle SCM (a.k.a Oracle Repository), PVCS and Clearcase.
    I would suggest you take a look at Otacle SCM
    Whic you allready own (part of the Oracle developer suite that forms is a part of).
    You will get a lot more functionality for Version control including diffing of fmb's etc from this tool.
    Check out the demo at : http://www.oracle.com/ip/develop/ids/index.html?repository1.html
    http://www.oracle.com/ip/develop/ids/forms_docs/formscm_viewlet.htm

  • Does Captivate 3 play well with Visual Source Safe?

    I am using Captivate 3 at my company. Is it safe for two of us, both with licensed versions of Captivate 3, to check files into Visual Source Safe so we can each check them out to make changes? The subject matter experts (SMEs) want to be able to make changes to content. Our output is Flash/HTML.
    SAM

    Hi Sam
    I don't mean to sound snarky here, but if you already knew the answer, why did you bother to ask?
    VSS is something known as a Source Control system. This normally means you check SOURCE files in only. In Captivate, there is a single source file. That file is the .CP file.
    The other files you referenced (.SWF / .HTM / etc.) wouldn't typically be added to VSS.
    However, I am aware that some folks prefer to use VSS as a repository for their developers to also use when they build output. So in some cases I do understand that folks add their output files to Source Control. If this is the case for you, certainly you would want to include the output files.
    Cheers... Rick
    Helpful and Handy Links
    Captivate Wish Form/Bug Reporting Form
    Adobe Certified Captivate Training
    SorcerStone Blog
    Captivate eBooks

  • Java and Microsoft Visual Source Safe

    Hi,
    We have content in text files stored checked in to Visual Source Safe.
    I want to provide a web interface that allows users to update this content.
    To do so I will need to programmatically check in/check out files from VSS.
    Has anybody implemented a similar system in Java? ideas where to start?
    Note: I am aware that Eclipse has a plugin for VSS so this must be possible
    Any help much appreciated.
    Thanks

    A similar situation like what I had a few weeks before.
    We will have an internal box that a user goes to and
    checks out a file via a web interface. I would have
    thought that only that box requires any kind of VSS
    plug in.
    Assuming i am stuck with VSS, then I would have hoped
    to be able to find an API that enables me to supply
    details of the VSS ini to establish a connection and
    then call simple methods like checkin() etc. Seems
    like its going to be a lot more complicated than that.SourceAnyWhere by Dynamsoft offers a pure Java client for VSS (both GUI client version and command line client version provided ). Have a look at http://www.dynamsoft.com/products/saw_overview.aspx
    It also provides a Java SDK for VSS ( I had not try this). I think the Java client would have solved the problem.
    HTH.
    Regards,
    Reggy

  • LabWindows integrated into Visual Source Safe

    Can you please help me. I just started with a
    company and my boss gave me a project to link VSS with LabWindows/CVI. I
    know LabWindows/CVI can be integrated into Visual Source Safe and I have
    asked the engineer's, which said it can be done and read the book, but still
    can't figure it out. Can you give me direction or examples, I'm just out
    of
    high school and want to make a good first impression.
    Thank you for any help.

    Wow Ken. Did you find a solution? We are thinking of going to VSS here for C code and it would be great to link in our CVI code as well. You are sure that you can huh? Let me know if it worked out for you.
    Grant
    Grant M. Johnson
    Project Engineer
    LECO Corporation

  • 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

  • Visual Source Safe w/ JDeveloper

    I stumbled on a couple of posts relating to this with a search but I just wanted some more clarification.
    Is there a plugin for Jdeveloper that would allow me to use the built-in source control with a MS Visual Source Safe repository?
    TIA!
    -jay

    Unfortunately there is not an extension to do this automatically.
    You could add to the external tools menu items to call ss.exe to checkout and checkin files.
    It's something we are trying to schedule for a future release, but no commitments yet.
    Thanks,
    Rob

  • Will Visual Source Safe work for non-Microsoft software as well as documents?

    We have software that was made by a subcontractor. It is used to control a machine with proprietary syntax. Will VSS archive it as well as Visual Studio things?

    Hi OilMan545,
    If you mean to use Visual Source Safe as a source control tool and use funtions that VSS provided, the answer is yes. You can use VSS to manage your source files. And it's recommended to use TFS since it's more powerful and in the spoort scope of MSDN forums.
    If you want to do the integration for the software and VSS, that depends on the functions that the software provided and whehter it has interfaces/plugin to interact with VSS.
    Best regards,
    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. <br/> Click <a
    href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

  • Why does LabVIEW8 popup error message after i use Visual Source Safe as its sourc control?

    i'm trying LabVIEW8.0 trial version now. and i set Visual Source Safe as its sourc control, just setting like following picture.
    but since then, LabVIEW8 always popups error message dialogue even when it starts up.
    it confuses me, for it runs well while i use LabVIEW6.1 before.
    following is some message dailogue.
    帖子被longzhi在04-03-2006 07:36 AM时编辑过了
    Too much works make Longzhi a Tom.
    Thanks god, the weekend is coming.
    And my lovers are always here with me.
    Anything better? ^_^
    Attachments:
    bug20060403_002.JPG ‏70 KB
    VSSConfig.JPG ‏82 KB
    bug20060403_001.JPG ‏33 KB

    hi, smercurio…
    i've tried your way. but it doesn't work. :-(
    but your idea helps me. i've tried some times and it's OK now.  thank you. :-)
    here are my steps. ( is it right? )
    1. start LabVIEW.
    2. Tools >> Options >> Source Control.  select source control provider name as my microsoft VSS.  no error message.
    3. Then set my source control as None. a warning dialogue popup, "You have selected not to use any source control provider". Yes to continue.
    4. exit LabVIEW
    5. edit LabVIEW.INI. delete the part of source control. ( like the attached picture).
    6. Start LabVIEW. and reset the source control as normal.
      Bingo! it's OK. :-)
    帖子被longzhi在04-03-2006 08:39 PM时编辑过了
    Too much works make Longzhi a Tom.
    Thanks god, the weekend is coming.
    And my lovers are always here with me.
    Anything better? ^_^
    Attachments:
    BugFix20060404_001.JPG ‏88 KB

  • XCode Integration With VSS (Visual Source Safe)

    We have recently start developing for iPhone using XCode. We already have Visual Source Safe in place as our source control and I want to give it a try (integrate with XCode) before thinking of using CVS or SVN.
    Sometime back TheSilverHammer talk about VSS integration with XCode in his post "Two questions: Xcode 2.4 (reloading a source file) and endianness ...", however it was not clear how he did that? This post is now archived and is no longer available for replies. TheSilverHammer can you, or anyone else please tell how is it possible?

    I don't really know about VSS/XCode integration but I have to make a comment. Dump VSS. Pour gasoline on it, light a match and run.
    There are so many issues with VSS I'm not sure where to begin. No scalability, terrible stability, proprietary, etc.
    You mentioned CVS and SVN. In the long run you'll be way better off with either of those. Personally I prefer SVN.
    Just my 2 cents

Maybe you are looking for