Does parameter files get exported along with workflow? - informatica

I exported the workflow from dev and imported into test. But the parameter file hasn't been copied to test along with wf. DO i have to manually copy the parameter files into test or is any procedure for that to do so.
Informatica powercenter
Thanks,
Teja

There is two ways to do this,
1) shared directory, in this you have to only give the path to the directory in which your parameter file is existing.
2) you have do the manually copy the parameter file into the test.

Yes you have to copy the parameter files manually.

It would be manually copied.
Note that the parameter might need modification as to the folder name if the target repository is different from test.

Related

Is there a way with conan to export an empty directory?

Considering a folder (called parent_folder) containing an empty folder (called empty_son_folder) and another one that is not empty (called not_empty_son_folder) and the following exports_sources method:
exports_sources = ["parent_folder*"]
Only not_empty_son_folder is exported.
Is there a way with conan to force to copy an empty folder in export source method?
As #Yumnosch said it is possible to add a dummy file to force conan to include this folder or create this folder later in the receipe (#drodri's solution).
If the need is to have files generated by some test programs, both solutions work.
It is also possible to create such a folder directly in the test program that needs it.

T4 template automatically check out output files from source control

I think it is common to let t4 template automatically check out files from TFS when transforming the template. But i transform the template, i got error:
Running transformation: System.UnauthorizedAccessException: Access to the path 'C:******.cs' is denied.
Is there any way to overcome it?
either check out the file first, or add a prebuild step to attrib the file before building.
It is not recommended to put generated files under source control. You should exclude them with .tfignore or .gitignore then delete them from your repo.
This will prevent the issue that you are experiencing.
As the files are generated on build there is no need to retain and already old version in source control.

Where to start for writing a shell script for copying elements into main app xcode4

I am looking for some documentation or tutorial for copying files from a given directory into the app created by xcode at build time, before it is run.
At first I have tried to copy files into the derived directory, hoping that everything resides in there would be automatically added to the app, but I was wrong.
So I am looking for a script because the original dir may change its name, second the script could be customized by another xcode 4 user with its src dir path etc.
The things is I don't know how to start, which language etc. I am quite confident with shell script, but maybe there's a better option.
Second, I am trying to figure out which command could add a file in the already built app.
thanks
That answer didn't really help - the BUILT_PRODUCT_DIR isn't where most stuff goes.
Ultimately, I found you just need to do:
Add the following to the very end of your script (or get your script to write directly to the output location):
cp ${DERIVED_FILE_DIR}/[YOUR OUTPUT FILES] ${BUILT_PRODUCTS_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}
...but there's a lot of other things I tried. More thoughts and ideas here: http://red-glasses.com/index.php/tutorials/xcode4-a-script-that-creates-adds-files-to-your-project/
You want a Run Script or Copy Files build phase. Select your main project in the navigator, then select the app's target. Click the Build Phases tab. Click the Add Build Phase button at the bottom of the window and choose the appropriate phase.
By "appropriate" I mean if you really want to run a script, you'll use a Run Script build phase and use Xcode-provided environment variables like $BUILT_PRODUCT_DIR (see the documentation or hit build and examine the full output of an empty script in the build log) to figure out your target folder. If all you want to do is copy files (no real processing), the Copy Files build phase already knows how to locate the app bundle's proper folders depending on what you're copying (Resources, Frameworks, etc.).

How to copy resource (any content) files to output folder when NUnit's shadow copying is turned on?

Of course there is an option to turn it off (by default it is on.) However I like to be able to make incremental changes to the DLL while a copy of NUnit GUI is up.
However I couldn't find much documentation for this feature (apart from the need)
So the problem is like this
With Shadow copy enabled in NUnit,
my SUT (Dll) invokes an executable (also in the output folder ; via references). Now this executable needs certain configuration/modifier files to be in the same folder as the executable. How do I ensure that my reference modifier files are reachable by the executable during the test ?
Does NUnit shadow copy just the SUT dll or all the linked/referenced dlls/execs ? What do I need to do in the test setup such that any supporting files for the SUT are copied correctly?
I see that
executingAssembly.Codebase gives me the original output folder
executingAssembly.Location gives me the shadow copy folder.
I'm not sure if I am being lucid here - let me know if I need to update
The real issue is usually finding where they are during the tests.
Use this instead of Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location):
string exeDirectory = Path.GetDirectoryName(new Uri(Assembly.GetExecutingAssembly().CodeBase).LocalPath);
See Trouble with NUnit when determining the assembly's directory

FinalBuilder Enumeration of files and folders

What's the best way to enumerate a set of files and folders using FinalBuilder?
The context of my question is, I want to compare a source folder with a destination folder, and replace any matching files in the destination folder that are older than the source folder.
Any suggestions?
ok, for future reference, it turns out that under the catgeory "Iterators" there are two very helpful actions.
File/Fileset Iterator
Folder Iterator
Further digging revealed the Robocopy Mirror action, which does exactly what I was looking for, namely syncing the destination folder with the source folder. No need to write my own file iteration routines.