I have an Excel add in created using the Yeoman generator and I'm trying to find where add in manifests are installed to on the Mac file system.
I know when you sideload the add in the manifest is placed in:
/Users/<username>/Library/Containers/com.microsoft.Excel/Data/Documents/wef
But this only allows the add in to be added as a developer add in every time you open Excel.
Is there a place where I can place the add in manifest to have it stay installed in Excel not as a developer add in?
Is this the correct way to distribute an add in to users without having the add in on the AppSource store or is there another way to distribute Excel add ins via .exe/.dmgs/.pkgs?
Any information about this process would be greatly appreciated.
There are several ways to deploy the add-in manifest. The details are in this section of the official docs: Publish.
Related
Add-in is already published on AppSource.
There is a new feature or bug fix implemented in .js file linked in taskpane.html of the official version.
Should an update to add-in be done using Partner Center or a simple update of linked .js file is acceptable?
We are using simple content update of linked .js files approach and we are facing 2 problems:
Some users need to clear cache manually to force Excel to download updated .js file.
Some users report that custom function call in workbook was expanded with prefix _xldudf_. (premise is that Excel recognizes a change of official assets and thus treats it as insecure)
I seem to only be able to create a new project from the "Quick Start" panel. And this screen is only available when you don't have any projects open.
I know I can close all projects, create a new one, then select File >> open recent if I want multiple projects up. But is it possible to create a new project, say from the File menu while I am already in another project? The only option for creation there is for new files for the current project.
Is it possible to copy/duplicate a project without having to copy/paste the file folders and then import?
I use Android Studio on Windows, so I'm not sure whether it's any different on OSX, but the File menu does allow for creation of new projects.
The screenshot below shows the File menu while a project is open. Note the highlighted item. If this is missing for you then you may have some problem with your installation - or the OSX version is seriously different, but I doubt that.
You could try resetting your installation to default (see here for instructions). Just be sure to backup the config files (instead of deleting them) in case this does not solve your problem.
The only other thing might be different on my system is that I do not use Gradle projects, but I don't really see how that would change this behaviour - but that might be the case.
I have a larger solution that I desire to distribute via ClickOnce. It consists of one main shell executable that directly references only a small subsection of libraries and processes that constitute the solution.
The solution consists of a few other processes and several libraries (some C++). I need to be able to include all of these libraries and processes in one ClickOnce distribution for both local builds and TFS server builds.
I cannot reference every other library and process form the shell project. And I do not wish to push these files into a MSI to be treated as a prerequisite as it would defeat the purpose of using ClickOnce to distribute/update the product.
What is the correct method to incorporate all of our necessary files/projects into a single ClickOnce distribution?
The IDE won't detect native DLLs as dependencies when publishing, but you can run the SDK tools directly to include them manually in your ClickOnce distribution. You can either use mage.exe in your post-build script or run MageUI.exe to have a wizard to guide you through the package generation.
Suggested reading:
Walkthrough: Manually Deploying a ClickOnce Application
Understanding Dependencies of a Visual C++ Application
There is an alternative to Visual Studio for this kind of situation. You could try using Mage, but it can be a little tricky to use. My company wrote an alternative called ClickOnceMore.
ClickOnceMore is a ClickOnce build tool for when you don't want or can't use Visual Studio to do ClickOnce builds.
There is a specific page on the UI for including files (using rules to include anything from a single file to an entire directory trees) so you should be able to do exactly what you need with it.
This is what I have done in a similar situation. I use TFS at work, so convert the terms to whatever you may use (or not use) for source control.
I have a main workspace that I use for all development of my application, I keep this workspace pristine.
I then created another workspace with a proper name (ex: solution-deploy) and in this workspace I do the following:
Get latest and merge everything from source-control into the deployment workspace
I build a Release build of my application
I r-click on the root (I put them in the root, because I need to access them from there, put them in whatever folder you want) project folder for my deployment project and select "Add -> Existing Item"
I browse in the file selector to the Release directory of the assemblies I want to add to my deployment package, select them, then I use the arrow next to the Add button and drop down to "Add As Link", do this for all of the assemblies you want to add and place them wherever you want them to be organized in your deployment
In the Solution Explorer, select the added assemblies and in the Properties window set the Build Action to "Content", this should be all you have to do, but others have had to also set the "Copy to Output Directory" to "Copy Always", I don't do that
Run a Release Build
Go to the Properties view for your deployment Project
Go to the Publish Tab and Click on the Application Files button
Your files should all be available and added to the Deployment
Set up your ClickOnce settings however you need them to be
Publish your ClickOnce package
Your published package should contain all of the assemblies you need now.
Keep your separate Deployment workspace set up this way and never check it in. Do your work in your development workspace. Whenever a new deployment is needed, open your solution in your Deployment workspace and get the latest code, build, then publish.
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.
Hello everyone and good day!
Question: I had create a Basic InstallShield Project in my MSVC2010, added some files and primary outputs and press build. Project compiled normally: there was created MSI, setup.exe, setup.ini and (WTF?!) local directory structure of files, which I'm trying to install (for example, "Program Files\My Company\app.exe, ..." files was copied there). I throught that this is not needed folder, so copied my setup files (MSI, setup.exe, setup.ini) to another folder and start installation. When process of installation come on to copy state, installer gave me the error, that no required files (app.exe,...) was found.
Does anybody solve this problem? I think this is the simple one.
Thanks!
You can achieve this by making some changes to the properties in solution explorer. This is so simple as you can compress all in single .exe file. Follow the given below step:
Right Click On Entire solution and Choose Properties as given below
Second step as you can see the dialog box. click on configuration Properties
Third Step
Last step
This is finest and easiest way to achieve the required task.
Answer was found by myself, but thank you all any way...
To create a self-extracted install file you need to open "Releases" tab in your InstallShield Basic project and right click on configuration click "Release WIzard...".
All what I need is at this figure:
Select Compressed from Compression option in properties view.
Simple use the "single image" build. Not cd nor dvd