Project File Reload SCC Integration

Hello,
We have LabVIEW integrated with our source control system, using SCC.
When we make a change to the project file, e.g. add a VI, this checks the project file out and applies the change. On occasion we get the message "The file <project file> has been changed on disk by an external action. You will need to reload then poject to reflect this change"; .e.g some has worked locally for a while and has gone to get the last version of the project from source control.
To perform this reload we are having to exit LabVIEW and re-start it, otherwise we sometime get a locally cached version.
Is there a better way of forcing it to reload, preferably automatically?
Thanks, for the help
Jon.

jonnnnnnn wrote:
In contrast with a VI, you get a popup box that asks you if you would like to revert to the disk version (which has just been extracted from source control) and loose you're changes, that would be OK as a sloution for the projectbut we never see that popup.
Jon.
Project present a larger scoping problem with trying to revert them. You could have many VI open from the project and those VI could be edited with unsaved changes or running. You could be connected to a target or performing other actions controlled by the project. Rather than causing loss of work by automatically attempting to reopen the project, that exercise if left to the user. There could be issue with trying to force shutdown running VIs and leaving resources uncleaned (if using hardware) and so forth. With VIs, the scope is much more limited and so we present the option to revert the file for you.
The recommended process for dealing with this situation is to always get the latest version of the project before starting any development to make sure that it is up to date. You can then take advantage of a menu option on the project file itself - "Get Latest Version of All Files". This option will list all the files in the project including any new ones that you don't currently have and get the latest version of the files.
George M
National Instruments

Similar Messages

The project file ' ' has been renamed or is no longer in the solution.

Hello Folks:
   Developing on Win 8.1 Pro, Visual Studio 2010 Pro, C++.
   I'm revisiting a project I haven't touched in over 2 years.
   Attempts to build result in a pop up displaying this error:
      The project file ' ' has been renamed or is no longer in the solution.
   And the build terminates.
   Things might have changed in the underlying static libraries used by other projects.
      I've looked through the Solution Explorer and the project's properties "Framework and References" window but I don't see anything with such an odd name.
   How do I resolve this problem?
      Thanks
      Larry

Some other things to try:
1. Reload each project in the solution (Right-click/Unload Project; Right-click/Reload project). See if any of them has an issue reloading.
2. If you have multiple projects in the solution: Make a copy of the solution and load the copy. Go in Build Dependencies and uncheck all. Now build each project individually and see which one has the problem. (Some of them might not link
due to missing libraries, but that's OK. You just want to see that the build starts). Double-check which configuration Visual Studio picks when it builds each project; if they are not all the same, the problem is with the project configurations.
3. Load the solution file with the XML editor. (Make sure no other Visual Studio instance has the solution open when you do this). Check each Project line for oddities, specifically, empty or mangled names, or missing project files. Also
check the Configurations. It could be that the problem project doesn't have an equivalent configuration to the one you are building. Sometimes the configuration definitions in the solution file get messed up.

'Out Of Memory' issue and over large Project File...

Hi everyone, my issue is a common one but yet to find out reasons why after trying many suggestions.
I am working in Final Cut Pro 6 on an edit 35 minutes long. It's a holiday video edit of a snowboarding trip filmed on GoPro HD and a small handy Sony Handycam. All rushes are transcoded to ProRess 422. I have cut the edit and doing the final touches with the colour using Synthetic Appertures Color Finesse 3. My project file starts off at a mere 17MB before colour grading/correction from what I can tell seems pretty normal. By the time I get to around half way my Project ile has increased greatly to over 70MB, FCP becomes slow and unstable then I start to get crashes and reloads of the project take around 15 minutes or more to open. This seems quite a jump to me once grading starts?
Originally I did have around 6 sequences of footage (one for each day of shooting on holiday) where each contained all the usable clips I could possibly use for the edit. Then a Master sequence where I would paste my desired clips to for trimming and editing to music. (all music in AIFF)
I have deleted all folders in the browser that arent in use now and the only sequence I have now is the master, nothing else at all! No Motion graphics but some text at the start of the edit, nothing animated. No stills, but I do have some freeze frames but I'd say no maore than 20 over the whole 35 minutes. I have deleted unused render files and trashed preferences.
I did see somewhere that someone suggested splitting the edit in to two different projects? There wasnt a clear explanation of this.
I'm running....
iMac 24 inch - early 2009
2.66 GHz Intel Core 2 Duo
8GB 1067 DDR3
NVIDIA GeForce 9400 256 MB
OS X10.8.2
Hope this is all you need to help me get this edit completed and exported off. Any more info you need just ask!
Thanks in advance.
GK

Hi Nick
I have already successfully rendered 20 minutes of the project with no issues. As the project file has increased it has become troublesome. Beach balling when pasting the colour finesse attributes to my next clip for instance.
When I attempt to render now its instantly fails with a "Out Of Memory" error and eventually crashes FCP.
Thanks.

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.

Perforce SCC integration problems

This is more of a bug report than a question.
We are using CVI/LabWindows together with Perforce as the Source Code Control provider and have noticed a couple of problems in the integration. Versions used (tools/platforms):
* Win7 (x86, x64)
* Perforce P4V 2010.2
* Perforce SCC plugin 2010.2
* LabWindows 2010
Problem 1 (bug)
Having a P4 workspace root in the workspace/client specification that differs only in casing from the actual path is causing the problems, even as we are working under Windows. Description:
- We can associated a CVI workspace with a Perforce workspace using "Edit/Project/Source Code Control" etc (we do get some initial warnings when we do this for the first time, but after reopening the project all is well).
- If the P4 workspace root path has the wrong casing compared to the actual local path, the project can be successfully opened and operations are available under "Tools/Source Code Control", but the files in the project (which do exist in Perforce) does not show any SCC overlay icons.
This makes it impossible to check out/work with the files contained in the project. As an example, it is e.g. possible to add a new file to the project and get the "add to source code control" dialog opened and select OK to add the file to the project/SCC. After this the file is still not indicated as under source control (opening e.g. P4V correctly shows the file as being opened for add, though). Similar for other operations.
We have reported this to Perforce software as well, but as we haven't seen the same problems for other software using the P4 SCC Plugin, it's likely to be a problem with the CVI SCC integration.
The problem is easy to fix once you recognize it, but diagnosing this took the better part of two working days.
Problem 2 (bug)
This one is easy enough to work around, but annoying. When performing SCC operations on the project file, the overlay icon isn't updated to reflect the new status automatically. An example:
If you right-click the project file and select "Check out", the file is checked out from Perforce and made writable, but the overlay still indicates that the file is not checked out. This makes it "impossible" to check in the file again. Same goes when opening a project with the project file checked out and the checking it in.
To get the correct status for the project file, one needs to either restart CVI or select "Tools/Source Code Control/Refresh Status". Highly annoying.
Problem 3 (bug/usability)
There is no simple way to check in all files currently checked out, when one these files is the project file.
It is possible to multi-select files and include the project file in the selection (using ctrl + left mouse), but when then right-clicking one of the selected files to perform "Check in" the other previously selected files lose their selection. This is only the case when the project file is included in the selection.
The same behavior is shown when selecting as above, but attempting to use the "Tools/Source Code Control/" menu.
The problem seems to boil down to that when several files are selected in the project, and one of them is the project file itself, only one of the files remain selected when opening a menu (any menu).
Regards,
Johan Nilsson

Sorry, I didn't see this until today.
Your first two issues definitely sound like bugs, or at the very least poor behavior. My guess is that #1 is probably our fault, but I'm not completely sure on that. I'm filing a bug report on this to make sure it gets investigated. #2 will also be looked at.
While your third issue is a little annoying in this use case, there's a reason for it. When you right click on an item in the project tree, we have to determine what type of object it is, and then display the approriate context menu accordingly. Projects and Source files have completely different context menus, and most of the operations you can perform on the two are different. For simplicity and a better user experience we only display the context menu for the item that was right-clicked on, and we deselect other files of that type. We won't be changing this.
Thanks for reporting these issues.
Kevin B.
National Instruments

Please Help, Missing Project File and Discussion Advice Isn't Working.

Here's the rundown:
I was working in iMovie HD 5 when the power got cut out on my external hard drive. When I try to reload my project I got the 'Missing Project File' error that has been discussed by many on this board.
There are two known fixes.
1) Open the package and go back to the '~' version of the project.
2) Use the MovieTimeline.mov in the Cache to import it back into a new project.
Solution #1 simply didn't work.
Solution #2 imports the full video as a single long clip but is significantly lower in quality than the original version.
In addition, the movie was shot in true widescreen and plays in quicktime in 16:9 mode, but when I import that .mov file into iMovie HD for some reason bars are added on the sides and top and bottom of the frame, and the bars are thicker on the sides so it stretches the picture and makes everything look taller.
Although I'd certainly much rather have my original project timeline back, I could still continue my work if I could figure out how to import the .mov so that it retains the quality and size that it had to begin with.
Does anyone have any idea how to import it without losing the quality and size or how to gain back an earlier project save?
Please help if you can, my grandfather's 83rd birthday gala celebration (2 days away!) depends on it!

I know you're in a rush, so I'll mention a couple other possibilities.
Solution #2 imports the full video as a single long
clip but is significantly lower in quality than the
original version.
• You shouldn't see any difference. The video imported from the Timeline Movie.mov is exactly the same as the original video. My guess is you're seeing some side effect of the widescreen issue. That, or your iMovie playback settings have changed.
In addition, the movie was shot in true widescreen
and plays in quicktime in 16:9 mode, but when I
import that .mov file into iMovie HD for some reason
bars are added on the sides and top and bottom of the
frame, and the bars are thicker on the sides so it
stretches the picture and makes everything look
taller.
• Make sure you're importing to a DV Widescreen project.
• It might work to open the Timeline Movie.mov in QT Player Pro and export to a DV stream set to 16:9, then import that to the new project.
• It's curious solution #1 didn't work. What happened when you tried that?
Karl

My premiere project file size just went from 190MB to 5.61GB... and now it won't open! Anyone know how this happened?

My premiere project file size just went from 190MB to 5.61GB... and now it won't open! Anyone know how this happened? Or how to prevent it from happening again? Thankfully I saved a backup project of the 190MB file size.

warp stabiliser?

Using iMovie to save project files to external hard drive?

I have a MacBook Pro with very limited space on the internal hard disk drive. I also have a few FireWire external hard drives.
A friend recently gave me his Hitachi DZ-HS300A mini-DVD camcorder so I could copy footage off of it, load it into my machine, edit it and upload it (several minutes) to YouTube. He can't do this because he lives in a remote area where there is no broadband yet.
I almost never use iMovie. I was wondering if there is a way to save the project file to an external FireWire drive so that there will be no large video files clogging up my laptop's internal hard drive. Can this be done? Is there an iMove preference I have to change?

You should generally leave the iMovie Project file on the boot drive. The Project File is mainly a small text file with in and out points.
The iMovie Event file is where the video assets are stored. You can store events to an external hard drive in two ways:
1) As you import from the camera, you will see an import screen. You can select the external drive on the import screen
2) If the event is already on your internal drive, you can click View/Events By Volume. Now you can drag and drop the event to the external drive in the Events SOurce List in iMovie.
For your external drive to be visible to iMovie, it must be formatted HFS+ or HFS+ (journalled).

"Unable to open project file" Error Message

I pulled an all-nighter (13 hours of editing) last night to create a critical project in FCE 3.5.1 on my Intel iMac running 10.4.11 then left this afternoon for a few hours and shut down my machine. Came back tonight and tried to open the project (which I saved on my Maxtor 1 TB external drive along with all of the scratch disk files). To my absolute panic, it won't open the file now with an error message that simply says, "Unable to open project file". HELP!!!! Anyone have any suggestions?!?!

In the past I found (and reported to Apple Feedback) the same bug Steve reports here, but I should recall that the problem:
- only appeared in PAL projects (probably not the case for kscritch) - never heard of it in NTSC
- was consistent in FCE 3.x, not so in FCE 4
I made tests importing .psd images with transparency into PAL projects using FCE 4, and I had various behaviours: sometimes the project worked, sometimes I couldn't open the project again (as in FCE 3), sometimes I had error messages with inconsistent behaviour (msg like "file error", but the project opened and file was there...), etc. so I decided to do without.
Now I only import .tif or .png images when I need transparency
Piero

"Unable to Open Project File" - error

Does anyone know how to resolve an "Unable to Open Project File" - error. I accidentally shut down my computer wrong, although Final Cut wasn't open.

Welcome to the forums.
The project file might have gotten corrupted. Look for the AUTOSAVE VAULT (typically in the DOCUMENTS>FINAL CUT PRO DOCUMENTS folder) and open the most recent version. Copy it to your main project folder if it works.
If not, then try trashing your prefs with FCP Rescue.
Shane

Error reading project file : no protocol

I have followed the instructions exactly as in the j2ee tutiorial ,but, when I run asant , an error occurs:
: Error reading project file : no protocol: ../../common/targets.xml
Urgent!

Could you please provide a bit more detail such as which sample you are using? Also are you using the latest version of the tutorial and have you configured your build.properties in the samples/common directory?

Using a JAR file as a project file

My application allows the user to create projects. Previously, a project file was simply an XML file. Now, a project file needs to also contain many images.
I thought it would be a good idea to simply use a JAR file as my project file.
Since I've really never really worked with JAR files and the java.util.Jar package directly, I have a few questions.
1) Would it be better just to simply store the images as binary in the XML file? I just spent a good amount of time making the XML file very readable so I thought it would be better to keep the images separate while still having a single "project" file.
2) Is there anything inherently wrong with the way I'm working with the JAR file in the code below?
Simple XML file:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE project [
<!ELEMENT project (img+)>
<!ELEMENT img EMPTY>
<!ATTLIST img src CDATA #REQUIRED>
]>
<project>
     <img src="blah.jpg"/>
</project>
import java.io.*;
import java.util.jar.JarFile;
import javax.xml.parsers.*;
import org.xml.sax.*;
import org.xml.sax.helpers.DefaultHandler;
public class LoaderTest {
    private String imageName;
    public LoaderTest() {
        InputStream i = null;
        JarFile jf = null;
        try {
            jf = new JarFile("project.jar");
            i = jf.getInputStream(jf.getJarEntry("project.xml"));
            // Here's my simple XML parser to load the project and images
            SAXParser parser = SAXParserFactory.newInstance().newSAXParser();
            parser.parse(new InputSource(i), new DefaultHandler() {
                @Override
                public void startElement(String uri, String localName, String qName, Attributes attributes) throws SAXException {
                    // Right now we only care about images
                    if (qName.equalsIgnoreCase("img")) {
                        imageName = attributes.getValue("src");
            // Load the image from the inputstream
            java.awt.image.BufferedImage img = javax.imageio.ImageIO.read(jf.getInputStream(jf.getJarEntry(imageName)));
            // Display the image in a JFrame
            javax.swing.JFrame f = new javax.swing.JFrame();
            f.setLayout(new java.awt.BorderLayout());
            f.setSize(800, 600);
            f.getContentPane().add(new javax.swing.JLabel(new javax.swing.ImageIcon(img)), java.awt.BorderLayout.CENTER);
            f.setDefaultCloseOperation(javax.swing.JFrame.EXIT_ON_CLOSE);
            f.setVisible(true);
        } catch (ParserConfigurationException ex) {
            ex.printStackTrace();
        } catch (SAXException ex) {
            ex.printStackTrace();
        } catch (IOException ex) {
            ex.printStackTrace();
        } finally {
            // Do our best to close the input streams
            if (i != null) {
                try {
                    i.close();
                } catch (IOException ex) {}
            if (jf != null) {
                try {
                    jf.close();
                } catch (IOException ex) {}
    public static void main(String[] args) {
        new LoaderTest();
}Thank you!

1) I also think it's much better to keep your images separate from your XML, this prevents a lot of in case you just want to read XML data
2) What's exactly going wrong here? For the project.xml, make sure it's not inside a directory within the JAR file, or else the variable i will be null. Otherwise it looks fine..

I was working on a project a few days ago and now I'm not getting any audio or visuals out of it. In the project file the screen went grey. Not sure how to fix this. I'm new to iMovie, but the program seems easy to use and my Mac is new. Any help?

I used to use Movie Maker and it would be able to handle lots of file uploads and big projects. I figure iMovie can do the same since it's newer and it's on my iMac. I was working on a project for a few months, it was working fine up until about a few days ago when the project file just stopped working. Not getting any audio or visuals and the screen went grey. I hope to not lose the project file as I've spent a lot of time on it. The project will still show up in iMovie, but it won't play. Other project files will, but this one won't for some reason. It's my first time using this program and I assumed it would be fine, but now it's causing me big problems. Anyone else run into a similar problem?

But it is I jsut can sync, back up files, or anything becuase its stuck at this screene and wont do execute when i click either of those button

Need help badly. project file wont open. saying damaged file or may contain outdated elements. please help

project file wont open. damaged file or contains outdated elements message. i believe its an XML error but i dont know how to fix it. please help

As a happy user of the Matrox RT.X2 for many years, and later an equally happy user of a Matrox MXO2, I can say from experience that it is highly unlikely that this problem has anything to do with the Matrox hardware!
Can you open a new blank project, and save it?
If you cannot import your faulty project into a new project, can you import the sequence from your faulty project?
Have you tried clearing the Media Cache, clearing your preferences, etc. - all among the techniques used to resurrect a Premiere Pro project that has gone bad???

How to change default value in "Project file" dialog

I'm new to Labview, and I've encountered an example with a dialog that allows to define a path to a file. If I open the properties on the block diagram of this block the name of the block appears to be "Path Properties: Project file:" The default value points to a different place than where the file installed and the VI won't run untiI I change the path. If I save and open the file, it doesn't remember the change. When the vi is running I can right click the text and there is an option to reinitialize to default. I've rooted around all over the place and can't find where this can be set or changed. How do I change this?

On the front panel, change the control to the desired value.
Now, right click on the control, select Data Operations and Make Current Value Default.
-Matt Bradley
************ kudos always appreciated, but only when deserved **************************

Project File Reload SCC Integratio​n

Similar Messages

Maybe you are looking for

Project File Reload SCC Integration