I want to use text-based integrations, which works only on default language.I want to change the default language of agent from de to EN.
My problem was solved. For those who might face the same problem, Below are steps.
Export the project as a Zip. (settings-> export/import )
Create a new Agent with the required default language.
Import the downloaded project from zip
(settings-> export/import ).
Note: there's another option of restore from zip, which will not change the default language, so don't do that.
Also, you have to change service account dependencies as we do for a new project. Thanks (solution got from try and fail, didn't have any documentation which tells the solution).
Related
what is bundle installation script in netsuite and its purpose. I tried it to
Suite Answers but could not figure out. Any help regarding to topic will be valuable.
thanks.
There is only two cases where I have seen it used.
To use it as part of license management. A bundle installation script can check with a third party system to check if the account where the bundle being installed has a valid license.
To check if the features that your bundle needs is activated or available in the account it is being installed on.
The bundle installation script can also be used for data migration, when the bundle is updated. ie Suppose in the newer version of the bundle, you are adding one new custom field. For the existing custom records in the customer account, if you want to default that custom field to a particular value, after the bundle update, then you can do the same via bundle installation script (Using the afterInstall hook)
One of the newest features in VS 2012 is the ability to create Private Extension Galleries, which allow you to build your own extension repositories and not have to publish them to the world (internal company tools, etc.). I've successfully created one as described in the MSDN blog I referenced, but I'm wondering if anyone knows of a way to programmatically set the details of the gallery - the name and URL, and then "Apply" it - so that each person who wants to access it doesn't have to manually enter in the info.
I looked in the registry to see if I could install a key, and I think it's possible but not exactly trivial. Anyone have any insight?
The registry keys to set are documented under http://msdn.microsoft.com/en-us/library/hh266735.aspx. $RootPath$ would indicate a path like HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0 on the user's machine. Minimally, you could write a little tool that just sets those registry keys.
If you want to be really fancy, you could take that .pkgdef example and stick that inside a .vsix. Then, installing that extension would register the private extension gallery. A bit meta, but that could prove useful.
I'm going to mark Jason's answer as accepted, because he pointed me in the direction of how to properly do it which was my ultimate question. However, I do want to add another solution which does work if this is all you need:
If you manually add your private gallery details to Visual Studio, your registry key will be created for you. Go to:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\ExtensionManager\Repositories\[Dynamic Guid]
and export that key to a normal .reg file. You can then either create a simple batch script to install the key for you on other computers, or just have people use the .reg file to install it themselves.
I created my iPhone app with MonoTouch and deployed it to the AppStore. Now I want to add a free lite version of the same app. What is the best way to do this with MonoTouch/MonoDevelop?
So far I created a new Provisioning Profile for the lite version. I can change the build options to use the full or the lite profile. But what else do I have to change and how? I think at least the app name should be changed, but how???
Thanks,
Christian
The way I do these things is to create a new project, then add the existing c# files from the first project as a link. You will see this option on the "add existing file" dialog. Keep in mind all your Icon/Splash screen files will have to be copied though, MonoDevelop doesn't handle these right if they are linked.
Just a side note, you can get by with less provisioning profiles. Create one as com.yourcompany.*, then name your apps com.yourcompany.yourapp1, yourapp2, etc.
So I have a profile for Development, AdHoc, and AppStore, but I have several apps deployed.
Rather than link files, I prefer to make three projects: A library project which will have all the UILogic called X.Touch.Core and two more which will have a reference of the Core. X.Touch.Lite and X.Touch.Premium. This way you don't need to have linked files, it can be painful. You can put a file called settings.xml and perform some feature toggling there.
In our company we regularly create MSI's with Installshield(latest).
These setups adhere to a set of rules and name schemes so they work with our deployment system and autobuilds etc.
Is there a way to eliminate the repetitive overhead of going through all the boilerplate stuff (setting the company meta data, basic folder structures, a few events, including some default helper files etc) for each setup?
Take a look at the InstallShield Automation interface. What I did was:
Abstract all my components out into WiX Merge Modules ( could be IS merge modules though ).
Create a base InstallShield project ( Common.ISM )
Create XML files to describe my feature tree and product configurations
Create Build Automation to reflect the XML and invoke the Automation Interface to "Emit" my installer source.
Build the Product Config in the ISM.
This gave me a great deal of code reuse but it's not trivial to set up this type of system. However it scales very well and the advantages are huge if you have the right business needs.
There are two ways you can do this:
Save the ism file in xml format (there is a setting for this in the project settings). Then in run time, push the desired values with a new application that could be written (which will edit the XML file using DOM or so...)
Use InstallShield Automation interface. This can be done using VBScript. You may check this link: InstallShield Automation Interface
I am in a development environment and have edited the site map using the following steps
-
creating an unmanaged solution
added existing site map
exported solution as ummanaged
edited customisations.xml
zipped up files and give same zip file name as exported solution
reimported solution into same environment
this has worked ok, but how should i now migrate these changes to a different environment namely training and ultimately live environment. Do i export as a managed solution and import into train/live or do i customise the site map on ea`ch environment
thanks for any advice
richard
As you should not modify the sitemap in your production/training organization I would recommend to export it as managed solution. With the managed approach it's possible to update the solution later on or to revert the changes by deinstalling it.
An unmanaged solution is more like a logical container. If it's imported into an organization, the changes are not reversible.