Project Difference in Labview with Serena Version Manager

We are using Serena ChangeMan Version Manager (integrated) with LabVIEW. And I was wondering if there was anyways for us to do a "Project Difference" in the LabVIEW. We need the ability to do a difference between what is in the Version Manager database and what is in the working directories. This is the most effective way to tell what changes have been made. Without this management of the software baseline will become difficult and time consuming. This is also very useful during the new development stage. There are often occasion when people have forgotten to check files in. Which cause a problem when attempting to build testers from the version manager baseline. This is easily avoided if the developer can do a difference of the development area to the version manager repository. VSS provide this feature and highlights the following in different colors: differences indicating if a file is in the repository but different from the local file, if the file is checkout, if the file does not exist in the repository or if the file exist in the repository but does not exist locally.
We are using LabVIEW 8.0 with Version Manager 8.1
Message Edited by Harsh324 on 05-17-2006 07:47 AM

Harsh324,
So once you have Serena configured in LabVIEW are you able to right-click in the project and select Show Differences? As mentioned in this tutorial the Graphical Differencing feature is only officially supported by Visual Source Safe and Perforce, however you may be able to get some information from this. I am not familiar with Serena, so it could be possible that it has something similar built in as well.
Please let me know if you get any results by selecting the option from the project. Thanks!
Andy F.
National Instruments

Similar Messages

Does Dreamweaver Work with Serena Version Manager

Does Dreamweaver Work with Serena Version Manager? If not,
what does everyone use for source control?

Harsh324,
So once you have Serena configured in LabVIEW are you able to right-click in the project and select Show Differences? As mentioned in this tutorial the Graphical Differencing feature is only officially supported by Visual Source Safe and Perforce, however you may be able to get some information from this. I am not familiar with Serena, so it could be possible that it has something similar built in as well.
Please let me know if you get any results by selecting the option from the project. Thanks!
Andy F.
National Instruments

Question about Starting Eclipse with PVCS Version Manager Plugin and Flash Builder 4 plugin

I used Eclipse 3.4.2 SR2 with PVCS Version Manager plugin.
I installed Adobe Flash Builder 4 Plugin to the Eclipse.
Eclipse executed successfully at first time.
After I open *.mxml file with the Eclipse and close.
After minutes, I execute Eclipse.
But I waited 40 minutes to see Eclipse Editor screen.
Are there any problem in Adobe Flash Builder 4 Plugin?
====== If you know Korean Character, You can see below message, I hope so ========
Environment
* OS: Windows XP SP3
* Eclipse: 3.4.2 SR2
* JDK: 1.5.0
* Serena PVCS Version Manager : 8.3.0
* Adobe Flash Builder 4 Plugin
위의 환경에서 Eclipse에 Version Manager Plugin을 설치하여 사용할 때는 잘 동작 하였습니다.
하지만, Adobe Flash Builder 4 Plugin 을 설치하고 *.mxml 파일을 열어 작업한 후에 Eclipse를 Close 하였습니다.
잠시후에 다시 Eclipse를 실행하면 약 40분 정도 시간이 지나서야 Eclipse 편집창을 볼 수 있었습니다.
혹시 Adobe Flash Builder 4 Plugin 제품과 Serena PVCS Version Manager 제품이 서로 conflict 하는 것이 아닌가
의심을 하고 있습니다.
귀사에서 이런 경험이 있다면 해결 방법을 알려주시면 감사하겠습니다.
Thank's

I experimented with the latest Zend Studio 8 trials on both platforms yesterday, and it looks a little different depending on which platform you're using:
On OS X, because Zend Studio is now contained entirely within the app bundle, it's tricky navigating to the proper eclipse folder with our Plug-in Utility. As it turns out, the Zend dropins folder does exist if you look down low enough:
/Applications/Zend Studio.app/Contents/Resources/Java/dropins
When I typed that path into the Burrito Plug-in Utility manually, it found the dropins folder, and proceeded to install the link without complaint. However, the Zend dropins folder is not working properly on OS X either, as already found on Win, so it's not using the link.
On Win, Zend Studio 8 doesn't include the dropins folder in the first place, as noted earlier. Apparently, Zend doesn't have its dropins folder enabled on either Mac or Win.
To see if this problem is specific to dropin links, I downloaded the latest Orbit plugins from eclipse.org and tried adding those directly to the Zend dropins folder, instead of using a link. Zend doesn’t appear to recognize them either.
I'll check with our contact at Zend to see what happened.
-Chris

How can I read pdf files from LabVIEW with different versions of Acrobat reader?

How can I read pdf files from LabVIEW with different versions of Acrobat reader?
I have made a LabVIEW program where I have possibility to read a PDF document. When I made this LabVIEW program it was Acrobat Reader 5.0.5 that was installed on the PC. Lather when the Acrobat Reader was upgraded to version 6.0, there was an error when VI tries to launch the LabVIEW program. And Later again when we upgraded to Acrobat Reader 7.0.5 I must again do some changes and rebuild the EXE files again
It isn't so very big job to do the changes in one single LabVIEW program, but we have built a lot of LabVIEW programs so this take time to due changes every time vi update Acrobat Reader. (We have build EXE files.)
The job is to right click the ActiveX container and Click "Insert ActiveX Object", then I can brows the computer for the new version of acrobat Reader. After this I must rebuild all the "methods" in the Activex call to make the VI executable again.
Is there a way to build LabVIEW program so I don't have to do this job every time we update Acrobat Reader?
This LabVIEW program is written in LabVIEW 6.1, but I se the problem is the same in LabVIEW 8.2.
Jan Inge Gustavsen
Attachments:
Show PDF-file - Adobe Reader 7-0-5 - LV61.vi ‏43 KB
Read PDF file.jpg ‏201 KB
Show PDF-file - Adobe Reader 5-0-5 - LV61.vi ‏42 KB

hi there
try the vi
..vi.lib\platform\browser.llb\Open Acrobat Document.vi
it uses DDE or the command line to run an external application (e.g. Adobe Acrobat)
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Moved Premiere Elements 10 project Error: "Project is not compatible with current version of Premiere Elements"

After moving an entire client folder from an external hard drive to an internal one, the client's video, created in adobe premiere elements 10, will no longer open in adobe premiere elements 10. It appears to be loading the project, and instead of completing, the following error message is displayed: "The project is not compatible with current version of Premiere Elements."
The same thing occurs when attempting to open the archive files.
New projects, and unmoved projects behave properly.
Moved projects receive this error.
I'm running Windows 7 Home Premium SP1 on a solid state drive (SSD) (c:/), where premiere elements is installed
My documents, including the project I need to work with are on my "storage" drive (HDD). it is (f:/)

txnoda
Archiving Aspects of this.....
First let clear the matter of the "archiving" as a life saver.... We do not appear to be on the same wave length.
a. I am talking about File Menu/Project Archiver with its Archive project and Copy project options. This feature is a safety net to save you when you
inadvertently disconnect source media from the project file. With the Archive option (Trimmed Folder result), you get saved to the computer hard drive (safe keeping) a copy of the project file plus copies of the media that were taken to the Timeline. With the Copy option (Copied Folder result), you get copy of the project files plus copies of much more.
b. Instead, you appear to be talking about "archiving" in the context of AutoSaves. AutoSaves are saved snapshots of the project at various phases of the edit. They suffer from the same shortcomings of the original project that has been disconnected from its source media.
When you import media into a project, all you get are copies of the originals in the project. But, those copies need to trace back to originals at the locations where they were when first imported into the project. Moving, renaming, deleting files/folders that went into the project after the project save close leads to some very time consuming messy situations.
What to do....
If you can, put everything back the way it was. If not.....
Let me emphasis some factors..
You wrote
After moving an entire client folder from an external hard drive to an internal one, the client's video, created in adobe premiere elements 10, will no longer open in adobe premiere elements 10. It appears to be loading the project, and instead of completing, the following error message is displayed: "The project is not compatible with current version of Premiere Elements."
Here you mention specifically "client's video". Later you detail with .mod files converted to .avi. What kind of .avi? If you have converted to AVCHD.avi or H.264.avi, they have been found not to be compatible with Premiere Elements. You should not be able to import them into any new or old project.
From what you described, I am envisioning
"Video" Folder
which contains 2 folders named
"Timestamped Folder" with .avi files
and
"DVD" Folder with the project file (project.prel)
The project file has many files generated automatically in the course of it workflow. Where do you have them going?
(See Premiere Elements 10 Edit Menu/Preferences/Scratch Discs). If you have the Scratch Discs directed
"Same As Project", then we would expect all those files to be going to the DVD Folder in the above scenario.
If we could open the project and get greeted with some "Where is the file.....?" messages, that might give us some hope.
But that is not the case.
Consequently from what you have said, I am suggesting that the path of least resistance is try to recreate the "before".
Please review and consider.
ATR
Add On...Not sure if it will assist in the matter, but the following is the link to Adobe's document related to troubleshooting
damaged projects.
Troubleshoot a damaged project file | Adobe Premiere Elements

JDeveloper integration with Serena PVCS Version Manager

I have seen that Oracle JDeveloper 10.1.3 now supports Serena Dimensions for versioning. What about Serena PVCS Version Manager 8.1? Are there any plans to integrate JDeveloper with the PVCS Version Manager?

Hi all,
Ward - Brian is absolutely right. As I said in my first posting on this topic (above), we have
not yet developed an extension for JDeveloper to enable users to work with PVCS Version
Manager, which I believe is a specific product, rather than an interface.
This is why I'd greatly appreciate it if you could possibly provide more details of this Interface
and indeed what Oracle support for PVCS with JDeveloper Merant referred to. Please see my
first posting above for more details.
Brian - I'm sorry you do not agree with our approach of using the open published SCM Framework
to build your own extensions for using JDeveloper with other source code control tools than those
we support.
In an ideal world, we would have been able to offer support for every source code control tool on
the market with our first release of 9i JDeveloper. We were very keen to be able to achieve this and
we still plan and are currently looking into supporting more tools going forward and as many tools as
possible in the long term.
Unfortunately, we only have limited time available for each release and based on the feedback we
received, after our committment to support Oracle9i SCM, CVS and ClearCase were the most requested.
Therefore, we tried to reach a compromise to enable users to provide their own support for a specific
tool should they wish, if they did not use any of those tools supported. Indeed, our research suggests
that the market for source code control tools is quite fragmented and that customers use a wide range
ot tools. So, we decided to publish our own SCM Framework, the same one we used for the SCM, CVS
and ClearCase support, in order to help users build their own extensions in a similar way to ours.
Hope this helps,
Regards,
Dominic Battiston
JDeveloper Product Management
Oracle Corp

Working with version management and promotion management best practices BO 4.1

Hi Experts
I wondered if anybody knows if there is a document or something about best practices to work with the version management and promotion management in BO 4.1?
Our Environment includes two servers. The first one is our development and test server. The second server is our prod system.
Now on the dev server we have basically two folders called dev and test. We control access to them with a right system based on the folder structure.
My question now is how you would work in this scenario (third server is not an option). Main target is to have as few reports as possible. Therefore we try to work with the version management system and only have one version of each report in the dev folder of the cms. But this is where problems start. Sometimes the newest version is not the version we want to publish to the test folder or even prod server.
How would you publish the report to the other folder? Make a copy of the concerned report (transport to the same system via promotion management is not possible). Also how would you use the version management in regards to the folder structure? Only use version management in dev folder and export reports to test folder (out of vms control) or also use vms in test folder and how would that work?
Further more I’d be interested in learning best practices with promotion management. I found out that the promotion of a report that doesn’t exist in prod doesn’t make any problems. But as soon as an older version already exists there is only partial success and the prod folder gets renamed to “test”.
Any suggestions on how to handle these problems?
Thank you and regards
Lars

Thank you for your answer.
So you are basically proposing to work with the vms in the dev folder and publish the desired version to the test folder. And the test folder is out of version control in this scenario if I understood you correctly (like simple data storage)?
And how would you suggest promoting reports to the prod system? Simply by promoting the
desired version from dev folder directly to prod? This would probably lead to inconsistence because we would need to promote from dev system to test and dev to prod instead of promoting a straight line from dev over test to prod. Furthermore it would not solve the problem of the promoting result itself (A new folder called dev will be generated in prod but the report gets promoted to the prod folder if there was no report before).
Thank you for the link. I came across this page just a few days ago and found also lots
of other tutorials and papers describing the basic promoting process. The promoting process in general is clear to me but I wondered if it is possible to change some parameters to prevent folder renaming for example.
Regards
Lars

PVCS Version Manager Interface to Jdeveloper -- need help with install

Several of our developers are using Jdeveloper and we need to know how to install the PVCS Version Manager interface to JDeveloper.
I have already contacted Merant, the vendor for PVCS Version Manager and they could only confirm that the interface existed but was supported by Oracle.
I have not been able to find any documentation on installing this interface.
Can anyone supply directions or point me to someplace to look for them.
Any help you could give me would be greatly appreciated.
Ward

Hi all,
Ward - Brian is absolutely right. As I said in my first posting on this topic (above), we have
not yet developed an extension for JDeveloper to enable users to work with PVCS Version
Manager, which I believe is a specific product, rather than an interface.
This is why I'd greatly appreciate it if you could possibly provide more details of this Interface
and indeed what Oracle support for PVCS with JDeveloper Merant referred to. Please see my
first posting above for more details.
Brian - I'm sorry you do not agree with our approach of using the open published SCM Framework
to build your own extensions for using JDeveloper with other source code control tools than those
we support.
In an ideal world, we would have been able to offer support for every source code control tool on
the market with our first release of 9i JDeveloper. We were very keen to be able to achieve this and
we still plan and are currently looking into supporting more tools going forward and as many tools as
possible in the long term.
Unfortunately, we only have limited time available for each release and based on the feedback we
received, after our committment to support Oracle9i SCM, CVS and ClearCase were the most requested.
Therefore, we tried to reach a compromise to enable users to provide their own support for a specific
tool should they wish, if they did not use any of those tools supported. Indeed, our research suggests
that the market for source code control tools is quite fragmented and that customers use a wide range
ot tools. So, we decided to publish our own SCM Framework, the same one we used for the SCM, CVS
and ClearCase support, in order to help users build their own extensions in a similar way to ours.
Hope this helps,
Regards,
Dominic Battiston
JDeveloper Product Management
Oracle Corp

Diffing Files in LabVIEW with Perforce?

I've read the sections of articles about doing a graphical difference in LabVIEW with Perforce here: http://zone.ni.com/devzone/cda/tut/p/id/4631#toc4 and here: http://decibel.ni.com/content/docs/DOC-1681#Graphical_Differencing, but I still can't get it to work!
When I right click on a VI from the Project Explorer that is checked out and select Show Differences... Perforce complains that it doesn't know how to do the diff on the files. I assume this is because I haven't told Perforce about the LabVIEW Diff features or the .vi file extension types. How do I this? Is there an article I missed somewhere that describes this step by step?
Edit: I forgot to mention, how do I use the Compare VIs tool in Tools -> Compare -> Compare VIs? When I do this it bring up a dialog in which the first field is the VI I have open. The second field is blank, and that is the VI that I would compare the VI open to. However, since I am using Perforce, the previous file revision are in Perforce. How do I tell this dialog to compare it to a file that is in Perforce?
Thanks in advance!

In the LabVIEW help there's a LVCompare.exe topic; under that, look at "configuring source control with." Following the directions there will allow you to show differences directly from Perforce. However, within LabVIEW, this shouldn't be necessary -at least, it's always worked "right out of the box" for me with no further configuration. Which of the two LabVIEW Perforce clients are you using? You may need to use the command line version in order for differencing to work properly.
Compare VIs does not work the way you seem to expect for VIs in source control. It simply compares any two VIs loaded in memory. To compare with the latest version from Perforce, use Tools -> Source Control -> Show Differences. If you want to compare something other than your current version versus the most recent revision in Perforce, you'll need to execute the diff from within Perforce.

Version Management of ODI interfaces

Dear All,
In a development envronment, if I need to configure, my ODI environment with any version managent system, what are the steps?
which version management systems could be used for the same and how?
How versioning of ODI objects is managened during development, ? is there any standard proces of mentodology to follow?
Suppose I created an interface and saved it as Interface1.0 and then modified is further and saveed it as Interface1.1, now I want to go back to Interface1.0 because the logic in the latest version was not appropriate and would like to restrat from Interface1.0 as a baseline. How to retrive older object? Is there any tool oracle proivdes for such version managemnt of ODI objects? if not can we use any other version management system to do the same? Wht is the process?
Thanks and Regards

Its difficult to explain the details about version management in ODI. Please refer the document for better understanding.
http://docs.oracle.com/cd/E28271_01/integrate.1111/e12643/versioning.htm
Also for your second question, you can restore from latest version to the previous version. This is also included in the document.
Thanks.

Setting up Version Management (Git, SVN) for Captivate Projects

I'm guessing the answer is No, but I thought I would ask:
Is there any way to set up some kind of Version Management/Source Code management for a Captivate project?
Currently, I just have a bunch of nearly identical cptx files with some kind of naming convention so that I can tell which one is which. If I need to revert something, I have to hope that I made a "Save As" at the right point in time. If I need to work with a colleague, there is no straight-forward way to review the changes that she made.
Adobe Captivate is basically a speciallized IDE with some additional graphical stuff. Having some kind of version control tool, especially if it were Git, would be very helpful both for my personal productivity as well as for managing collaboration with my colleagues.

So far the only WOW version control i have found is AlienBrain but i have a better chance of being struck by lightning on a clear summer day than ever owning it.
http://www.alienbrain.com/features
A promising solution is Razuna http://razuna.org/whatisrazuna but I havent "project tested" it yet to see how well it will work while developing in a team enviroment.
Something i doubt i will ever find is a solution to "show the difference" in a file similar to how WinMerge http://winmerge.org/ shows the difference in files or compairison of folder directories.
It would be nice to be able to compare two (or more) captivate files slide by slide with syncronised scrolling to note differences.
Seems like most people are pretty quiet about what they use for version management.

Version Management with Analysis workbooks? Doesn't save workbooks in BW Netweaver platform or BO Platform

SAP BusinessObjects Analysis, Edition for Microsoft Office - 1.4 SP6
SAP BusinessObjects BI Platform - 4.1 SP2
BW 7.3
SAP Logon pad - 7300.1.0.1074
We are trying to implement What-if analysis in Analysis Office tool like Revenue increase by N percentages. Excel formula applied for this in the adjacent column to keyfigures that is coming from BEx Query.
Here, I need to save the Workbooks in versions as V1, V2, V3, etc., for various percentages.
When I try to save this in BO platform, only the version V1 (first copy) is getting saved. But, the modified workbook is not getting saved with different name as V2 or V3, etc.,
When I try to save this Netweaver platform, even the first copy V1 is not getting saved. But it displays different versions in the save window before closing the Analysis Office application.
Please provide information on VERSION MANAGEMENT with Analysis Office.
Note: I see a difference in 'Open' and 'Save' window that is Roles are not visible in the 'Open Workbook' window but Roles are visible in 'Save Workbook' window.
Thanks,
Jeni.

SAP BusinessObjects Analysis, Edition for Microsoft Office - 1.4 SP6
SAP BusinessObjects BI Platform - 4.1 SP2
BW 7.3
SAP Logon pad - 7300.1.0.1074
We are trying to implement What-if analysis in Analysis Office tool like Revenue increase by N percentages. Excel formula applied for this in the adjacent column to keyfigures that is coming from BEx Query.
Here, I need to save the Workbooks in versions as V1, V2, V3, etc., for various percentages.
When I try to save this in BO platform, only the version V1 (first copy) is getting saved. But, the modified workbook is not getting saved with different name as V2 or V3, etc.,
When I try to save this Netweaver platform, even the first copy V1 is not getting saved. But it displays different versions in the save window before closing the Analysis Office application.
Please provide information on VERSION MANAGEMENT with Analysis Office.
Note: I see a difference in 'Open' and 'Save' window that is Roles are not visible in the 'Open Workbook' window but Roles are visible in 'Save Workbook' window.
Thanks,
Jeni.

Robustness "Managed Driver Beta" with earlier versions of clients

Hello,
i have tested the "Managed Driver Beta".
It works well.
It really is a great relief to distribute only a reference.
I have a production system in a live environment.
It is very important that there are no disturbances.
Now to my question:
Is there really when using the "Managed Driver" no problems with already installed clients with earlier versions? e.g. ORANT?
Thanks
Armin

Yep. It's nicely self-contained in its own assembly and namespace and doesn't impact on other things. If you really want to be paranoid about it, distribute it with your project instead of installing it on the server directly. That'll put it in your project's \bin folder and no other code will even realize it's there.

Add management server: Setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0

I want to add another management server to our existing SCOM environment. But whenever I run this setup on a new server I get stuck in the window for selecting the OperationsManager database. The database field stays blank and in the OpsMgrSetupWizard log
there are lines that the setup version is not compatible with the database version. But I use the same installer as when I installed the other management servers a year ago.
Maybe there is a newer setup installer? But I can't find it.
[10:42:54]: Error:
:Error:setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Info:
:Info:isOMDatabase: Read returned true. so far, this is OM DB, not an empty DB
[10:42:54]: Debug:
:Connection was not open. We will try to open it.
[10:42:54]: Debug:
:SqlConnectionReady returned True.
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Info:
:Info:isOMDatabase: Read did not return true. The MG is missing. This is not OM DB
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Always:
:Azman store table not found in OperationsManagerDW table, assuming this is an not a valid OMDB for empty DB scenario.
[10:42:54]: Info:
:Info:DatabaseConfigurationPage: DB connection attempt completed.
[10:42:54]: Info:
:Info:DatabaseConfigurationPage: DB connection attempt completed.

Never mind, found it!
Apparently there was a newer version of SCOM setup in msdn and someone upgraded our existing SCOM environment. Downloaded the new setup, new report viewer controls and a System
CLR Types for Microsoft® SQL Server® 2012 and now it works!!

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

Any ideas?

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

Project Difference in Labview with Serena Version Manager

Similar Messages

Maybe you are looking for