Project File File References

Does JDeveloper 9.0.4 use absolute or relative file references in its project (.jpr) files, or is it a mixture of the two? I've heard conflicting stories but have personally only ever seen relative references.

Yes, I've tried this and have gotten a clean compile. However, the .dll is associated with third party software intended to add controls to a form. The form does not display in Designer though (extensive stack trace errors) which made me wonder
whether there is a downside to this approach.

Similar Messages

How to declare variable in solution file for use in project files.

Hi Folks,
Apologies if this is not the right place to ask, but I would like to declare a variable in my solution file that can used by all of the projects (prof files) in that solution.
More specifically in the project files, references are stored using relative paths which cause issues if they don't exist. I would like to replace the relative paths with a variable set in the solution file that can easily be changed when the solution is
built in a different location.
So I would like to replace "../../../SomeProject" with "$(SomeLocation)/SomeProject" but set the $(SomeLocation) in the solution file.
Regards
Andy

Hello Andy,
Here is a common sln file:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2013
VisualStudioVersion = 12.0.30723.0
MinimumVisualStudioVersion = 10.0.40219.1
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "wpf_EntityFramework", "wpf_EntityFramework\wpf_EntityFramework.csproj", "{A282940A-5F76-4FF8-9568-8B7D14133259}"
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Release|Any CPU = Release|Any CPU
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
{A282940A-5F76-4FF8-9568-8B7D14133259}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{A282940A-5F76-4FF8-9568-8B7D14133259}.Debug|Any CPU.Build.0 = Debug|Any CPU
{A282940A-5F76-4FF8-9568-8B7D14133259}.Release|Any CPU.ActiveCfg = Release|Any CPU
{A282940A-5F76-4FF8-9568-8B7D14133259}.Release|Any CPU.Build.0 = Release|Any CPU
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
HideSolutionNode = FALSE
EndGlobalSection
EndGlobal
And the Global Interface in the solution file is actually used for Visual Stuido add-ins. To know details, please read the following MSDN article:
1. Persisting Information in Projects and Solutions
Here you can find "If the Globals object is associated with the
Solution2 object, then the value persists in the .sln file. These values are persisted when the solution file is saved."
2.
Solution2 Interface
It's about the solution interface.
As you can see although they may save something to your solution file, it is not intended for you to use it in your project.
What's your projec type and can you alter to use some common ways?
For example:
1. If it is in project level, set your value public so that all classes can access the value.
2. Or you can choose to create a xml/text file or any file that you can read by code, and then read the value out from that file.
It will be much better than thinking about set value in the solution file.
Best regards,
Barry
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.

LV RTE cannot open project files that have .lvlib references in Dependencies

I'm writing a LabVIEW DLL to inspect LabVIEW project files, and I've noticed that if a project has a .lvlib reference in its Dependencies, then the Run-Time Engine contradicts itself about whether or not it can find the project file:
Project.Open returns error 7 (file not found)
Project.GetFileLVVersion is successful
Here are snippets from my G and C code that exercise this behavior:
int openStatus = StatusSuccess;
char* projectVersion = createStringWithLength(VersionStringLength);
printf("Analyzing %s\n", pathString);
OpenProject(pathString, &openStatus, projectVersion, VersionStringLength);
printf(" Project written in LabVIEW %s\n", projectVersion);
if (openStatus == StatusSuccess)
printf(" Opened project file.\n");
else
printf("Error: Could not find project file, or file was not a project file (error code %i).\n", openStatus);
However, when running in the development environment, both methods succeed.
Is this a bug, and if so, is it fixed in LabVIEW 2014?
Here is how you can reproduce it:
Prerequisites:
LabVIEW 2013 SP1 32-bit
ConEmu for a good console -- https://code.google.com/p/conemu-maximus5/wiki/Downloads
minGW for compiling a program to use the LabVIEW DLL -- http://sourceforge.net/projects/mingw/files
.lvlib reference in Dependencies breaks Project.Open in LV RTE
Unzip the attachment into a temporary directory (eg c:\xtra\temp)
Open "OpenProject.lvproj" in LabVIEW.
Build "Open Project Library".
Using ConEmu with a bash prompt, navigate to the temporary directory.
Type make
$ make
patching file `builds/platdefines.h'
gcc -std=c99 -g OpenProject.c -o OpenProject.exe -lOpenProject -Lbuilds
6. Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Analyzing c:\xtra\temp\OpenProject.lvproj
Project written in LabVIEW 13.0
Opened project file.
7. Notice that both invoke nodes execute correctly.
8. Type OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
Analyzing c:\xtra\temp\OpenProjectWithLvlibDep.lvproj
Project written in LabVIEW 13.0
Error: Could not find project file, or file was not a project file (error code 7).
9. Notice that the version node succeeded while the open one failed.
10. Type diff OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
$ diff -u OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
--- OpenProject.lvproj Tue Nov 4 11:28:28 2014
+++ OpenProjectWithLvlibDep.lvproj Tue Nov 4 11:32:37 2014
@@ -13,7 +13,11 @@
<Property Name="server.vi.propertiesEnabled" Type="Bool">true</Property>
<Property Name="specify.custom.address" Type="Bool">false</Property>
<Item Name="OpenProject.vi" Type="VI" URL="../OpenProject.vi"/>
- <Item Name="Dependencies" Type="Dependencies"/>
+ <Item Name="Dependencies" Type="Dependencies">
+ <Item Name="vi.lib" Type="Folder">
+ <Item Name="NI_MABase.lvlib" Type="Library" URL="/<vilib>/measure/NI_MABase.lvlib"/>
+ </Item>
+ </Item>
<Item Name="Build Specifications" Type="Build">
<Item Name="Open Project Library" Type="DLL">
<Property Name="App_copyErrors" Type="Bool">true</Property>
Here is another way to trigger this behavior, which also shows that LabVIEW only sometimes tidies the Dependencies item:
Open "OpenProject.lvproj" in LabVIEW.
Add a new VI to the project and place the "Application Directory" file path constant its block diagram.
Select "File » Save All (this Project)" and use the default name for the new VI.
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Remove the "Application Directory" file path constant.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice the problem is gone, as is expected.
Re-add the "Application Directory" file path constant to the block diagram.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is no problem, which is surprising as there should be an error since the Dependencies item hasn't been tidied.
Close the new VI and remove it from the project.
Select "File » Save All (this Project)"
Open "OpenProject.lvproj" in a text editor.
Notice the Dependencies item has been tidied.
Re-add the VI back to the project.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Solved!
Go to Solution.
Attachments:
LVRTE_OpenProject.zip ‏10 KB

NInjaneer_wow wrote:
The same behavior occurs in LabVIEW RTE: a new project with an Application Directory constant in a blank vi will return error 7 - file not found, but still return the correct version of LabVIEW in which the project was created.
I've been experimenting with workarounds for this behavior, and I found one.
When I provide the LabVIEW path for libdir in my executable's ini file, the run-time is able to load and inspect the project file.
libdir="C:\Program Files\National Instruments\LabVIEW 2013"
While it's expected that a stand-alone executable may be placed on a system that doesn't have the LabVIEW IDE, it's still surprising to me that the Run-Time Engine cannot find LabVIEW's standard library without some explicit guidance. What other considerations contribute to that behavior?
References:
LabVIEW configuration file/Paths -- http://labviewwiki.org/LabVIEW_configuration_file/Paths

A File Reference and its evolving life!

Hi all,
I've noticed something that came as a little bit of a surprise to me, but I think I have the explanation, at a hand-wavy higher level anyway. What I have not established is if this is a 'bug' or a 'feature', and if there are any ways the following issue can be avoided at the NI function/api layer.
Consider the file open and file close function. You open a file, you use the reference to the file to write/read data, then at some point you close the reference and the close function spits out the file-path. Here are a couple of tid-bits you may not be aware of (that are easy to test):
Q1) After your application opens/creates a file and starts using the file-reference to make file writes, if an external source changes the file-name of that file... guess what will happen on your next write function call?
A1:: The write successfully updates the newly re-named file with your new data without producing an error or a warning. (At least this is the case if your program is running on a vxWorks cRIO target and the file-name is changed directly on the cRIO via an FTP browser.)
Did this surprise you? It did surprise me! -My handwavy explanation is that the file-pointer is perhaps managed/maintained by the OS, so when the OS tells the file-system to rename that file, the pointer that LabVIEW holds remains valid and the contents of the memory at the pointer location was updated by the OS.
Q2) Continuing from the situation setup in Q1, after writing several new chunks of data to a file now currently named something completely different than when the file reference was originally created, you use the close function to close the file-reference. What do you expect on the file-path output from the close function?? What do you actually get??
A2:: The close function will 'happily' return the ORIGINAL file-name, not the actual file-name it has been successfully writing to(!). This has some potentially significant ramifications on how/what you can use that output for. At this point there is a ton of room for pontifications and more or less 'crazy' schemes for what one could do, but I argue that the bottom line is that your application has at that point completely lost the ability to accurately and securely track your file(s). Yes, you could list a folder and try and 'figure out' if your file-name was re-named during writing and you can in various ways make more or less good 'guesses' on which file you in reality just had open, but you can never really know for sure.
So, what do you guys think?? Is the behavior of returning the (incorrect) original file-path when you close the handle a BUG or a FEATURE?? Would it not be possible for LabVIEW to read back the data contained in the (OS?) pointer location and as needed update the file out path data when it closes a reference? Should we not EXPECT that this would be the behavior?
Q3) Again, continuning from the above situation, lets assume we are back at the state in Q1, writing data to a (re)named file. What happens if the file is deleted by an external process? What happens to the file reference? File function calls using the reference?
A3:: This one is less surprising. The file reference remains 'valid' (because it is a valid reference), but depending on the file function you are calling, you will get error such as error 6 (binary write reports this), or error 4 (a TDMS write will report this error), etc. So as long as you don't rely on file ref-num tests to establish if you are good to go with a file-write or file-action, you should be safe to recover in an appropriate way.. Just don't forget to close the file-reference, even if the file is 'gone', the reference will still remain in memory until you 'close' it (with an error)(?I might be wrong about this last part?)
I am not sure if the above is possible on e.g. Windows, Windows would probably prevent you from re-naming a file that has an open file-handle to it, but this is definitley observable on at least vxWorks cRIO targets. (I don't have PharLap ETS or RTLinux devices so I can't test on those targets.. if you want to test its pretty straigth forward to make a simple test app for it.)
[begin rant-mode related to why I found this out and why this behavior BITES]
There are situations where the above situation could cause some rather annoying issues that, for somewhat contrived reasons related to cRIO file API performance, CPU and memory resource management, are non-trivial to work around. for example, using the NI "list folder" to listing folders take a very hefty chunk of time at 100% cpu that you cannot break up, so polling/listing folders after every file update (or even on a less regular interval) is a big challenge, and if you are really unlucky (or didn't know any better) and gave the list command in a folder with 1000's of files (as opposed to less than about 100 files), the list will lock your CPU at 100% for 10's of seconds... Therefore, you might be tempted to maintain your own look-up table of files so that your application can upload/push/transfer and/or delete files as dictated by your application specific conditions... except that only works until some prankster or well-intention person remotes in and starts changing file-names, because then your carefully maintained list of file-names/paths' suddenly fall appart.
[\end rant]
QFang
CLD LabVIEW 7.1 to 2013

Hey guys, thanks for turning out your comments on this thread!
-Deny Access : still able to re-name (and delete) the file via FTP browser (didn't test other file avenues). I think this is for the same reason that NI vxWorks targets (such as cRIO-9014) do not support the concept of different users with different rights, as such, everyone have access rights to everything at the OS level. Another issue for me would be that "Deny Access" does not work on TDMS file references, so even if it worked, it would not help me.
--> I strongly suspect that these things are non-issues or issues that can be properly managed, on the new NI LinuxRT targets since (the ftp is disabled by default) it supports user accounts and user restrictions on files/folders. The controller could simply create the files in a tree where 'nobody else' has write access.
Obviously nobody should mess around with files on a (running) cRIO, but customers don't always do what they are supposed to do.
As far as the 'resources' or overhead to update the file-refnum with the new information, this would not be needed to be done in a polling fashion, simply, when the file-close function is called, as part of that call it updates its internal register from the pointer data, so this should be a low overhead operation I would think? If that is a true concern, a boolean input defaulting to not updating or a separate 'advanced close' could be created?
I've included a zip with the LV2013 project and test VI's (one for tdms one for binary) that I've used. nothing fancy, but in the interest of full disclosure. The snippet is the 'binary file' test vi, in case you just want a quick peak:
Steve Bird's findings of (yet) another behavior on Pharlap systems is also very interesting, I think!!
[EDIT] JUST TO CLARIFY, on vxWorks, the re-named file keeps being successfully written to, unlike the PharLaps' empty file that Steve Bird found.
QFang
CLD LabVIEW 7.1 to 2013
Attachments:
cRIO Tests.7z ‏30 KB

Any way to prevent dupes in Premiere Project file?

Due to working with both PluralEyes as well as multiple editors on the same project, I deal with importing a lot of XML and PRPROJ files into existing project files that I've worked with.
This, on a large scale, becomes untenable because every time I import another editor's work or a synced sequence, I get duplicates of all my media in the project. I'm trying to figure out if there any way to have Premiere check to see if the media is already imported, and reference that media in the imported sequence? If not, I will just keep getting larger and larger project files with multiple references to the same media, because both me and my other editors are working with the same media, but for different sequences.
As far as I can tell, when you import an XML, or even a sequence from another Premiere project, it creates new master clips for every clip used in the imported sequence. It does not recognize that you may already have a master clip that you're using in another sequence that is referring to the same media.
So if you want to keep both sequences in your project, you need to keep both master clips. If you delete a master clip from your bin, it will not stay in the sequence(s) that refer to it, it will get cut out, leaving a big steaming crater where it once was. Even if the sequence is not currently open. This is one of the things I loved about FCP7. You could delete every single one of your master clips and your sequence would be totally unaffected. You could even recreate the master clips by dragging them from your sequence to the bin.
I think if there really is no way to manage these duplicates, this is a HUGE problem for professionals who are working in environments with multiple editors. This isn't just a "well, learn how to deal with a new editing system" - this is actually a deal-breaker; and actually the only one that I see REALLY preventing Premiere from being the go-to choice for larger post houses. This problem becomes so big so fast that it makes true collaborative editing downright impossible. In my office we might have three people on a project, all editing and revising segments and passing them back and forth. On FCP7 this was easy as pie - we'd just cut and paste between project files and use basic versioning best practices. In Premiere, our project files quickly become nightmares and work is often inadvertently deleted or lost.
I would like to see:
- Smart media handling when importing sequences and projects. Premiere should look at the filenames and file location and attempt to relink any duplicate media. If it stumbles, it should ask for help like FCP.
- A media consolidation inspection feature. I'd love to see an option for inspecting your project for duplicate media references. When found, Premiere should automatically consolidate.
- Streamlined sequence exporting. You should be able to export a single sequence. I know there's some version of this in Project Manager, but we all know it should be easier than this!
Anyone have any ideas on how to fix this?

*******Enhancement / FMR*********
Brief title for your desired feature:
Link Master Clips to media on drives, not to sequences.
How would you like the feature to work?
"The selection you are deleting contains clip references in one or more sequences. If you continue these clip references will all be deleted. Do you want to continue?" In short, I never want to see this warning again. I *need* to be able to delete master clips from my project without having media deleted out of sequences.
Why is this feature important to you?
Editors need to stay organized from the beginning. Professional editors don’t edit birthday parties; we often have large quantities of different kinds of media, need to know where it is, need to access it quickly, and don’t need unnecessary things in the way.
Organization exists in one place: the project panel. The less that’s in the project panel, the smaller the project file size is, the faster the project file opens, closes and saves, but most importantly: the easier it is to find what you need, fast.
The reasons for working in multiple project files are endless. When you import a seq from another project, you also get the clips used in it. Often times these clips are already present in the project, which is why you now include a “don’t allow duplicates” checkbox in your import dialogue box (which btw doesn’t work when we’re working with Merged Clips painstakingly built in other project files).
While you might fix that Merged Clips bug, I still don’t know why you won’t just let me clean stuff up myself. Why are you trying to save me from myself? I know where my media is and Premiere knows where my media is: on my drive.
A professional editing program should not try to save people from themselves. It’s why I left FCP for you. You have a great, powerful suite of programs (that I’d pay a lot more for than I do now btw)… but I need to stay organized, not be unnecessarily prevented from doing so.
Please listen to us and make this fix.

How do I save Icon templates with the Project files?

My project files are stored in a folder, say, "My Documents\LabVIEW\My Project", and this folder, in turn, is saved under (Sub)Version Control. I'd like to include a sub-folder called "Icon Templates" that could contain the icon templates I'm using in this project, but they seem to be "forced" into "My Documents\LabVIEW Data\Icon Templates" (almost the same, but the "owning folder" is different).
Is there any way to change, preferably on a Project-by-Project basis, the default location for Icon Editor templates? I tried to figure this out, and saw that one could change where "3rd Party" templates were stored, but that didn't seem to do anything (maybe because I don't understand the concept of a "3rd Party"?).
An important (to me!) reason to accomplish this is that I want to commit my new icons when I commit the rest of the Project, and have them appear when I checkout the project on another machine (or do an update from the Repository).
Suggestions welcomed ...
Bob Schor

Well, I thought of this as well. I did change Default Data Documents (which seems to be where Icon Editor expects to find its Templates file) to My Documents\LabVIEW (instead of LabVIEW Data), and that worked (sort of). But that still doesn't solve my problem. I have multiple projects -- My Docs\LabVIEW\Project 1, say, and My Docs\LabVIEW\Project 2, and want to have a specific set of icon templates for each stored, say, as Project 1\Icon Templates and Project 2\Icon Templates.
My problem is two-fold. First, there is a setting in Icon Editors, Tools, that seems to be designed to let you designate where your "special" templates are located, which I've set to, for example, My Docs\LabVIEW\Project 1\Icon Templates. However, when using the Icon editor, these templates never appear! It's as though it's still "locked" into the "3rd Party" sub-folder of the parent Icon Templates folder. Second, even if this worked (which it doesn't), is there a way to "embed" this setting as part of Project so that the settings "stay with the Project" (and can thereby be customized)? One important reason to do this is to simplify organizing Projects and folders on disk -- I keep them "together" (use the same structure for both, so a Project is contained, on disk, inside a single set of nested folders), which greatly simplifies and facilitates using Version Control to manage development.
Thanks for the reference. I didn't know about all of the symbolic names. It does appear that they are only used in the VI Search Path entry, correct?
Bob Schor

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.

SSDT: Creation of localDB instances from project file - Sql Server Unit testing purposes

I have a SqlServer Database Project in my solution (VS2013 Professional) which has a corresponding test project with some stored procedure unit tests. Currently I am using a LocalDB and as far as I understand a local database instance is created in C:\Users\[User]\AppData\Local\Microsoft\Microsoft
SQL Server Local DB\Instances\Projects and the specific .mdf file referenced in the SQL Server Object Explorer is in C:\Users\[User]\AppData\Local\Microsoft\VisualStudio\SSDT\[ProjectName]. The unit tests run fine on my local machine which I have developed
the project on.
My issue is we have a box which is configured to check out the project file from our version control, build the project using ms build commands and then run the unit tests using VSTest.Console. Usually with C# Test projects we reference the test project
dll and the unit tests run fine. I have referenced the dll for the test project with the stored procedure unit tests in.
With the Stored Procedure unit tests however we get this exception:
Initialization method [project].[spTest].TestInitialize threw exception. System.Data.SqlClient.SqlException: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. The specified LocalDB instance does not exist.
After some digging I have realised that the localdb instance seems to be created when the project itself is created in VS not when it is built. Specifically when the localdb is first used and if you look into the appData folder of the test machine there
is no corresponding mdf file for the project.
The question is is there a way to set up a localDB instance on the new machine if all you have the project file? The only purpose of the project on the test machine is to run the unit tests, no other development purposes. VS2013 Professional is installed
on the test machine but a solution only using config file changes or MSBuild/VSTest commands would be preferable.
I realise you could change the connection string to an actual test database and run the unit tests of that but we quite like the localdb approach for the testing. I also realise that you could potentially transfer the mdf file (haven't tested this solution)
as well, though I would prefer if there is a solution to my initial question.
http://technet.microsoft.com/en-us/library/hh234692.aspx
http://msdn.microsoft.com/en-us/library/hh309441(v=vs.110).aspx
I have been reading up on LocalDB and I assume a automatic LocalDB is created when you create a sql server database project (ie on localdb first use). I have tried adding the database creation to the test project config file but do not really know where
to go from there. The second link does not really specify when the named localdb will be created if you add the config items and I am not even sure if that is an actual solution. Here's my test project config file for reference
<configSections>
<section name="system.data.localdb" type="System.Data.LocalDBConfigurationSection,System.Data,Version=4.0.0.0,Culture=neutral,PublicKeyToken=[PublicKeyToken]"/>
<section name="SqlUnitTesting_VS2013" type="Microsoft.Data.Tools.Schema.Sql.UnitTesting.Configuration.SqlUnitTestingSection, Microsoft.Data.Tools.Schema.Sql.UnitTesting, Version=12.0.0.0, Culture=neutral, PublicKeyToken=[PublicKeyToken]" />
</configSections>
<system.data.localdb>
<localdbinstances>
<add name="SimpleUnitTestingDB" version="11.0" />
</localdbinstances>
</system.data.localdb>
<SqlUnitTesting_VS2013>
<DatabaseDeployment DatabaseProjectFileName="..\..\..\SimpleUnitTestDB\SimpleUnitTestDB.sqlproj"
Configuration="Release" />
<DataGeneration ClearDatabase="true" />
<ExecutionContext Provider="System.Data.SqlClient" ConnectionString="Data Source=(localdb)\Projects;Initial Catalog=SimpleUnitTestDB;Integrated Security=True;Pooling=False;Connect Timeout=30"
CommandTimeout="30" />
<PrivilegedContext Provider="System.Data.SqlClient" ConnectionString="Data Source=(localdb)\Projects;Initial Catalog=SimpleUnitTestDB;Integrated Security=True;Pooling=False;Connect Timeout=30"
CommandTimeout="30" />
</SqlUnitTesting_VS2013>
Thanks in advance for any response. Sorry if there is any misunderstanding, while I have been using VS to develop from the start, this is the first time I have used a Sql Server Database Project.
Regards,
Christopher.

Yes, you can create a LocalDB instance manually. You use the SqlLocalDb utility, see here:
http://technet.microsoft.com/en-us/library/hh212961.aspx
Erland Sommarskog, SQL Server MVP, [email protected]

Can I Open RH5 project file in RH10?

I don't like registration of all kinds until I took an RH arrow in the knee. XDD
Here's my scenario:
My colleague created a project in RH5 long time ago and now she's handing over the project to me.
I copied the whole robo source files folder to my local disk and tried to open it in RH10. Then error saying .cpd file might be corrupt so that RH cannot load the data from the database. I know .cpd file is the cache file for a RH project, right? It's created/overwritten every time you open the RH project. Then I figured, maybe I should delete the .cpd file(as it might be created in RH5 in her machine) before I open it in RH10?
Also, I've tried to open the same project file in RH5(I have RH5 and RH10 installed in the same OS:Win 7). It worked for the first time, with lots of errors of broken links and reference links but failed for the second time, right after I opened that project in RH10. (You might will want to doubt if RH5 is executable in Win 7, I thought it should be but it turned out it is, which is amazing...)
So..here're the questions:
1. Do RH5 and RH10 coexist in Win 7? Some said they don't..
2. Should I delete the .cpd file created in lower version of RH before I open the project created in RH of lower version(say, RH5) in RH of higher version(in this case, RH10)?
3. Can RH10 open the project created in RH5? I know the project created in RH of lower version will be converted in some way when it's opened in RH of higher version. Anyone practiced this successfully?
Thank you!

It proves that X5 can be opened. It does not prove it will work properly in all respects. Also webhelp will likely have issues with some browsers. In other words and to answer your question, both can be on the same machine but that does not mean both will work as designed.
Rh8 could be used with Windows 7 when Rh8 was released, except bits broke until it was patched so the chances of X5 are rather low.
MS Access is not needed on your machine as the CPD is a runtime database. There's no point messing with it, leave Rh to recreate it.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Project Bloating and Repair in Premiere Pro CS6; Max Project File Size? Adobe Coders Welcome...

Greetings.
After a few browsing sessions, I haven't found direction for a specific problem within a project bloat. First and foremost; we're always backed up. I have a restoration copy of the project that I will reference herein. Check that off the list.
Numerous people have posted here and around Creative Cow with problems regarding an expanding file size using CS6; watching files go from 300mb to 2.8gb. The unfortunate problem is when the project crosses a magical line that results in an inablity to open, import, export, or access sequences contained therein. Has anyone addressed a solution to repairing Premiere CS6 save files? Reducing file bloat? I haven't seen anything (recall the FCP7 repair days... solutions existed because problems were frequent; thankfully not so bad with Adobe).
Does anyone inside the code size know the maximum project file size that Premiere can read? I created a monster... Over 200 sequences utilizing 4.5TB of footage, stretching from Red codecs to EXCam to MPEG4 and H264. And for some time, the project size was manageable. Then, it inflated. And one day, randomly stopped opening. None of the auto-saves open.
Just curious. Files aren't the problem, but the 2.8GB save file is. Machine specs // etc. are openly available if required; no bad ram, no problems with all projects (just this one beast).
Cheers,
Jon Michael Ryan

REALLY_ Mac has a history of being more stable than PC with Premier ...
Pastor Bernie
International Evangelism Coordinator
Global Teen Challenge
visit us on FACEBOOK (http://www.facebook.com/bernie.gillott) or on
twitter-just tweet globalcry
~~~~Pray Big or Stay Home~~~
www.bgillott.org (http://www.bgillott.com/)
426 Newport News Ave, Hampton VA 23669
Phone (757) 728-0347 cell (757) 218 8499
In a message dated 6/2/2013 5:50:50 P.M. Eastern Daylight Time,
[email protected] writes:
Re: Project Bloating and Repair in Premiere Pro CS6; Max Project File
Size? Adobe Coders Welcome...
created by joe bloe premiere
(http://forums.adobe.com/people/joebloepremiere) in Premiere Pro - View the full discussion
(http://forums.adobe.com/message/5373302#5373302)

Opening CC project file on second machine fails

Hello!
I believe I´ve read most or all of the matching topics here but I am still stuck, so here´s my situation.
On my primary Workstation I´ve created a project of medium complexity (150GB, approx. 200 files, 5 sequences).
Here everything is working just fine.
On my laptop I also installed Adobe CC. I copied the whole projects' folder from workstation 1 onto my external HDD and connected it to my laptop.
Opening and cutting works fine here too.
Now, when I save and take the project (project file only) back to workstation 1, here Premiere Pro CC fails to load it up.
The loading bar proceeds to about 75% and then freezes. If I give it some time (10-15 minutes) it finally finishes loading, but Premiere isn't showing any reaction to mouse or keyboard, there are no panels at all visible. Basically it is crashed, allthough that´s not being indicated by the task manager.
I´ve tried all the tips from in here as well as the "usual stuff":
Saving a new project file, nothing.
Deleting preview files, then saving a new file, nothing.
Importing the project into AE and exporting a new project (on my laptop), nope.
Deleting all dynamic linked comps from the old project, saving then taking it to laptop 1, opening and saving it again, taking it back to the workstation, no.
Completely deleting everything Adobe on my workstation 1 and re-installing CC, "great" experience, but to no avail.
I also followed the solution of the similar problem on another thread here in the forums, with unzipping the xml and deleting certain lines of code and so forth, still nothing.
Then I went ahead and installed CC on my second laptop (not at all to be considered a workstation). Here the projects saved on laptop 1 opened just fine (asking for media files of course...).
EDIT:
I forgot to mention that a new and blank project from the laptops opens just fine on the workstation...
So I have to consider that something's wrong with my primary workstation. Right?
Any ideas, anyone?
It´s a fresh installation of Windows 8.1 with 24GB of Ram, GeForce GTX 570, i7 950, WD drives only, Windows on a seperate hybrid disk...
All CC installations are up to date.
Any help would be greatly appreciated as my deadline is on monday...
Thanks!

Try assigning the same drive letter to the laptop's external drive that you have assigned to the media drive on your workstation. That way, any project saved on the laptop will have the same absolute media file references that the workstation has.
NB: If Task Manager still thinks that Pr is responding by showing you that it's using memory and CPU cycles, then Pr probably hasn't crashed. It's just busy and taking its sweet time about whatever it's doing. (Emphasis on "probably")
You mentioned deleting preview files, but you didn't say anything about cleaning your media cache. Try that. A good cleaning of your user and Windows temporary files might help. You should also run chkdsk on your workstation's drives to help you diagnose whether or not hard drive failure is imminent.
Cheers,
Jeff

Need to checkout MS Project file from Excel VBA

I have a VBA Excel macro that can open an MS Project file, and extract data. It works fine when the MS Project file is on my hard drive or other location where no check out is required. But often the MPP files I need to access are stored in SharePoint,
in document libraries, that have checkin/checkout enabled. I am aware of the the way to do this for an Excel file, such as the following code snippet.
' Determine if workbook can be checked out.
If Workbooks.CanCheckOut(Filename:=docCheckOut) = True Then
  Workbooks.CheckOut (Filename:=docCheckOut)
Else
  MsgBox "You are unable to check out this document at this time."
End If
I need to be able to do the same thing for MPP files. Here is the code I have; however, I get a compile error on the CheckOut line, indicating "wrong number of arguments or invalid property assignment". My research suggests that I should
get this compile error, as it only works on certain collections. Even the line containing "CanCheckOut", while it does not give me a compile or run time error, it does not return the proper response.
Dim mpApp As MSProject.Application
Set mpApp = New MSProject.Application
AppActivate "Project Professional"
' Determine if mpp file can be checked out.
If mpApp.CanCheckOut(mppFileToOpen) = True Then
  mpApp.CheckOut (mppFileToOpen)
    Else
        MsgBox "Unable to check out this document at this time."
   End If
Is there a way to checkout an MS Project file stored in SharePoint from within Excel VBA? Thanks.
Ray

Rod,
Thanks very much. This was, indeed, the solution. Don't know how I could have missed this.
I did run into some issues with ensuring proper object references, checking back in, and being able to handle files that may be on a laptop, SharePoint site with checkout requirements, or SharePoint site without checkout requirements. Also faced an
issue checking back in; part of my macro opens the MPP file (that is checked out), acquires various pieces of data, then runs a macro in the MPP file that exports data to an excel spreadsheet. After this macro runs (does a save-as using a map), check
in is no longer possible. Fortunately, I could checkout the MPP file, open it, get all the required data elements, make a few changes to the MPP file, check it back in (but not close), then run the macro, then close without saving. In the end,
it all works like a champ. Thanks very much for your advice.
Ray

Would working from a locked project file cause problems?

Hi all.
working in FCP 4.5 on numerous Dual G5s (2.0 & 1.8 GHz) with sufficient RAM (4 GB+).
I'm working on a large project with a number of editors and I've created projects that each editor can use as references to the material. I lock the reference projects so that if they inadvertantly make changes to them, they will be reminded that the changes will be lost when they close out of the project. A theory has arisen that we are seeing performance degredation due to conflicts with Autosave. By performance degredation, I mean that responsiveness decreases, and an occasional crash occurs. I'm just wondering if the concern is valid. I'm just wondering if the concern is valid. My feeling is that it's too intermittent to be autosave's fault. Has anyone come across this?
thanks,
jack

nothing is written to the project file between saves, so it seems unlikely that your issues are related to their lock status. autosave only requires that a project has a pre-existing project file in order to work, so again, the issue would sem to be unrelated
... ok, so much for logic. the real resolution is likely only to come with be some controlled trial and error. see how you get on with unlocked project files and see if the performance issues disappear.

To save each Project file in AIR application separately

Hello
I'm on the verge of developing a Desktop AIR application for a particular purpose. Now this application has the facility to develop multiple projects. What I would like to do is to save each of this project in a separate file in a specified location.
And moreover when I double click this project file, the AIR application should load with the specific project. My main purpose is to port project file of user's choice from one PC to another and open the same (assuming AIR application is installed in that machine) on double clicking it.
So if a user has created 5 projects inside the application and wants to share only one of the project, he/she should be able to do that.
A application that works the same way is MarketSamurai.
I hope I have explained it clearly my requirement, kindly please provide me suggestions.
Thanks

You can register file types, sure. Did you check the API reference ?

[svn] 4267: Change path to Assets.swf in eclipse . project file from full hardcoded path to use the FLEX_SDK variable as the base path .

Revision: 4267
Author: [email protected]
Date: 2008-12-09 10:32:36 -0800 (Tue, 09 Dec 2008)
Log Message:
Change path to Assets.swf in eclipse .project file from full hardcoded path to use the FLEX_SDK variable as the base path. There is still an issue with Assets.swf not getting referenced correctly. If you import the framework project from Blazeds/trunk into Eclipse and get an error related to Assets.swf or that says "Unable to export SWC oem" for the time being try right clicking on the framwork project in Eclipse and selecting properties. Then in the properties panel, select Flex Library Build Path and then the Assets tab. On the Assets tab, check the check box next to Assets.swf and click Ok. This usually fixes the reference for me.
Modified Paths:
blazeds/trunk/development/eclipse/projects/flex/3.0/framework/.project

Revision: 4267
Author: [email protected]
Date: 2008-12-09 10:32:36 -0800 (Tue, 09 Dec 2008)
Log Message:
Change path to Assets.swf in eclipse .project file from full hardcoded path to use the FLEX_SDK variable as the base path. There is still an issue with Assets.swf not getting referenced correctly. If you import the framework project from Blazeds/trunk into Eclipse and get an error related to Assets.swf or that says "Unable to export SWC oem" for the time being try right clicking on the framwork project in Eclipse and selecting properties. Then in the properties panel, select Flex Library Build Path and then the Assets tab. On the Assets tab, check the check box next to Assets.swf and click Ok. This usually fixes the reference for me.
Modified Paths:
blazeds/trunk/development/eclipse/projects/flex/3.0/framework/.project

Project File File References

Similar Messages

Maybe you are looking for