I want to create an Outlook Add-in that doesn't require a task pane, but just performs some automation based on launch events.
Is this possible? The yo office generator has an option to only generate a project with manifest, but there seems to be a lot of additional required stuff missing afterwards.
Should I go with a generated task pane Add-in structure instead and just remove unneeded things from it instead? I am not that experienced in web development, so I am looking for an easy way.
Is this possible?
Yes, it is possible. Task panes are not required for running Office web add-ins.
Should I go with a generated task pane Add-in structure instead and just remove unneeded things from it instead?
You may scaffold any project the yeoman generator suggests and remove all the unnecessary stuff from there. Ready-made generated skeletons are made for your convenience. But don't forget to update the manifest file in such cases, not only delete unnecessary files from the src folder.
You may find the Configure your Outlook add-in for event-based activation guide helpful.
Related
I've got some experience with this cool IdeaVim plugin and CLion and was pretty satisfied with it, but I am having a trouble which torments me at the moment.
Is there an ability to add custom mappings which could work in Project Tool Window? I have "set NERDTree" option in my .ideavimrc, but it seems there is no vim-way shorcuts for creating new files and some other useful actions.
How do I Remove a Temporary key in a C# Windows 8 App? I downloaded a template that has one and got the error it expired. Do I need to put in a key of my own? I'm sure the author wont care its just the C# Windows Store Grid App XAML) Template that visual studios ultimate 2013 provides. The author just added a background image to show people how to do that. I removed his image and put in my own.
I'm a total noob at coding this is my first time using visual studios. All I understand atm is web design and adding snippets and changing values of code as well as compiling it.
I like to open, open source code to learn from it and see how it works.
Within your solution, double-click on the "Package.appxmanifest" file. This should open up the "App Manifest Designer". Go to the Packaging tab. Click on the button labeled "Choose Certificate..." and choose a new certificate. Chances are you want "Create test certificate...". You don't need a password. Hit OK and you should be good to go.
If you're looking to sideload the app onto other machines at your workplace or upload the app to the app store, you've got quite a bit of other work to do -- but that is I think outside the scope of this question.
I have a console application that I've been developing and I'm just about ready to publish it for consumption.
However, there's a file that the app needs to reference (a couple files actually) and I'd like to try to include these either during install logic or via an outside process. Here's the situation:
The application fires off a load test based on some criteria the user chooses. The load test is defined by a .loadtest file which is created outside of this project.
So what I would like for the installer to do is contain the .loadtest files and just shove them in a default directory that the project can reference.
I can't figure out how to add this specific file as a pre-requisite or anything though, in the publish wizard. Any ideas?
When you add a file to the solution, it does not automatically get attached as part of the build in some cases. If you right click the file in your solution explorer and select "Properties", change the build action to "Content". This will ensure that VS includes the file as part of the build/publish and places it in the output directory of the build process.
In Visual Studio, we're using the click-to-publish thingy... is it possible to write a plugin or somehow give a confirmation dialog when you click publish to make sure that's what you want to do? don't want people accidentally overwriting production
I don't know is it possible to turn this on by default, but if not - at first you need to understand how VS does this. Probably this is some msbuild targets file (msbuild task) which has some settings like "Publish = True/False". So what you can do - is to create a new msbuild task which you will invoke before the Publish task (you can try to add this task to your project file). In your task you will check if "Publish = True" - you will show message box "Do you want to publish?" and if somebody will click No, you just need to override "Publish" value in msbuild to False. I think this should work.
I don't know of any plugin which can do this.
One approach to mitigate the risks would be to create multiple configurations combined with multiple publish profiles:
E.g.
configurations: Debug_Development, Release_Development,
Release_Production where, using web.config transforms, set
different settings for connection strings, app settings, etc. (a nice
introduction to web.config transforms, and not only, can be found
here)
publish profiles: debug_development, release_development and release_production, each of them with different ftp settings (if you deploy via ftp) and each of them connected to the corresponding configuration
As I compare many C# example projects to my VB.NET projects, I see that the References folder shows in the Solution Explorer without having to select "Show All Files". Is it possible to have this for a VB.NET project as well? I find that it would be very helpful to have this folder displayed without having to see all the other hidden files as well.
I'm using VS2010 Professional.
This adds to my list of reasons why I should have learned C# first...
I guess I will have to definitively crush your dream. Sorry. It has been a decision by Microsoft to remove this from the default view to reduce the 'clutter'. However, your 'Show All Files' setting will persist when you save your project. So if you show all files once and then save, then it will always be on.
You can also see your References in the Project designer, which you can always keep open in a tab.
As of Visual Studio 2015, this behavior has been changed to show the References folder without selecting Show All Files.
From MSDN:
What’s new is the References node. This used to be hidden and you had to click Show All Files to see it—but that also showed lots of irrelevant files.
This previous behavior might have made sense 10 years ago when you’d start with a Windows Forms project and it would generally have the right set of references. But it’s a reality of modern development nowadays that the References node is used frequently—especially to manage NuGet references. It’s a small but handy convenience to be able to find it easily in Solution Explorer.
I add a separate folder called Dependencies, add my dll's to it and check them in as described here. That way my dll's are always visible in the Solution explorer without having to turn on Show All Files.
Select 'Show All Files option' in the solution explorer.