Is there any way to control "Enable express" option of Azure ServiceBus in MassTransit?
I've found other options like "Enable Partitioning", "Enable Batched Operations" but not this one.
According to google search results it seems like it was supported.
Also I've found commented out line in sources of massTransit test.
configurator.Publish<PartitionedMessage>(x =>
{
x.EnablePartitioning = true;
//x.EnableExpress = true;
});
With the Azure v7 SDK (first integrated with MassTransit v7.3.0), the ability to create an express queue or subscription was removed.
Related
I have a use case to receive call-back event when user removes add-in from outlook or need to remove add-in using REST API. can any guide ?
OfficeJS doesn't provide any callback or events for that. Feature requests on Tech Community are considered, when the dev team go through the planning process. Use the github label: “Type: product feature request” at https://aka.ms/M365dev-suggestions .
I have an use case where the addin should be enabled on specific machines instead of all the machines automatically.
Does bt:Url field in manifest.xml support that ?
If the Url is unreachable, mail should be allowed by default instead of being blocked (which is the default response from Outlook)enter image description here
Is there any way to do this ?
There are several ways to bridge the gap (solutions for your scenario):
Administrators can disable the on-send policy by ensuring the user's group policy setting Block send when web add-ins can't load is set to Disabled. To manage this policy setting, you can do the following:
Download the latest Administrative Templates tool.
Open the Local Group Policy Editor (gpedit.msc).
Navigate to User Configuration > Administrative Templates > Microsoft Outlook 2016 > Security > Trust Center.
Select the Block send when web add-ins can't load setting.
Open the link to edit policy setting.
In the Block send when web add-ins can't load dialog window, select Enabled or Disabled as appropriate then select OK or Apply to put the update into effect.
In the onSend event handler you may detect the mailbox or call an external web service which can give the answer whether to run your workload for a specific user / mailbox or not. Following that way you will be able to run your stuff for particular users only.
Read more about that in the Install Outlook add-ins that use on-send artice.
Would Smart Alerts (in preview) help you achieve your goal here?
Note, you can specify SendMode option in the manifest for a Smart Alert. There are three options available - PromptUser, SoftBlock and Block. With the SoftBlock option, if the add-in is unavailable (for example, there's an error loading the add-in), the item will be sent.
I developed an office.js add-in using the ItemSend event. Everything works fine if external service available. But when i was testing send email operation for "unavailable service scenario" get an error like bellow:
"We're sorry, we couldn't access [Add-in Name]. Make sure you have a network connection. If the problem continues, please try again later."
and
"The add-in [Add-in Name] has prevented this item from being sent."
So the question is how to ignore add-in for this situation?
I am testing on web browser.
Thanks.
The group policy Disable send when web extensions can't load must be set to Disable on each applicable machine if you want to let users send emails if the add-in is not available. Read more about that in the Install Outlook add-ins that use on-send section of MSDN.
This is not possible at this time. The Item Send Add-ins are currently meant for mission critical and compliance apps, and if your add-in is not available then mail can not be sent. We are aware of the demand for a "softer" Item Send add-in that will allow for send to occur if your add-in is not available, but we do not have anything to announce at this time.
Note that the Group Policy "Disable send when web extensions can't load" does not affect this scenario, and is actually even stricter. If Outlook cannot retrieve manifests from the Exchange server, then all send will be disabled. That GPO is also meant for deploying compliance Item Send Add-ins and to ensure all your users have the latest manifests that you have uploaded.
I have the following code:
import { ActivityTypes, CardFactory, TurnContext } from "botbuilder";
export class MyBot {
/**
* Handles incoming activity, received from a user, processes it, and replies as needed
* #param {TurnContext} context on turn context object.
*/
public onTurn = async (turnContext: TurnContext) => {
const oauthCard = CardFactory.oauthCard("ms-graph", "Login", "Please sign in so I know who you are");
return await turnContext.sendActivity({ attachments: [oauthCard] });
}
}
When I run the bot in bot emulator framework, I see the login button. When I click on it however, it just opens an empty signin window that's all white.
I've also configured authentication in Azure:
Edit: I've also configured the app id and password in my .bot file.
There is an option to use Azure Service Bus in place of ngrok which may work for you. It functions much the same but gives you control over where your data is traveling when "tunneling", among other benefits. As it's an Azure service, it can live in the same subscription you already access.
In short, you'll create a local client application that connects your bot via a relay to the Azure Service Bus service. The service bus namespace/relay replaces the messaging endpoint in the bot settings in Azure (for testing). In this way your bot running on localhost can connect to external services. Just be sure to use the same endpoint in Emulator that you use in the Azure bot settings, including the "/api/messages".
The instructions found here can guide you thru the process of setting up and running. The steps are a little long looking but the process itself is fairly simple. There are two options to build: a .NET Framework and a .NET Core. I would recommend the "Framework" version unless you need to run this on a Mac. This isn't an official MS blog (yet) but expect it to show up there.
Hope of help!
I have a simple Bot created using Microsoft Bot Framework running on Azure and it was working fine on all channels. Until yesterday when it stopped working on Facebook messenger when a user chose a particular untested option.
These are the lines that get executed when the rogue option is selected:
string replyText = "I am not yet ready to answer this question. Please choose another option.";
switch (appointmentBookType){
case Option1:
//Call Option1 Dialog.
break;
case Option2:
//Call Option2 Dialog.
break;
I keep getting "Sorry, my bot code is having an issue" as a response to anything I type.
This is the error I see in the Bot Framework developer portal for facebook messenger:
"There was an error sending this message to your bot: HTTP status code InternalServerError"
I am only using dialogs with some HeroCards.
I do not use LUIS.
I have fixed the bug by handling this previously unhandled conditions.
Is there a way to restart the conversation after fixing the bug?
After some scouring, this finally worked: https://docs.botframework.com/en-us/technical-faq/#my-bot-is-stuck--how-can-i-reset-the-conversation