I'm trying to manually install the EPiServer scheduler service on a web server using installutil.
I run this at the command promp:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\installutil D:\EPiServerSchedulerService\EPiServer.SchedulerSvc.exe
And get an error:
No public installers with the RunInstallerAttribute.Yes attribute could be found in the D:\EPiServerSchedulerService\EPiServer.SchedulerSvc.exe assembly.
It turns out it's not possible to do this with installutil, the service doesn't support it. I used the installer EPiServerShared.msi which is included with the EPiServer CMS downloads.
I wrote a quick blog post about it.
Related
I am facing below error while trying to launch logic app from VS code locally . I created logic app after installing extensions like -
Azure tools
Functions app tools extension v3.x
Logic App (Standard) extension
Azurite
ngFork for webhook
Below is the error I am getting when I click on overview from VS code -
Also my workflow is basic and simple as below -
Any help would be appreciated ! thanks !!
I have done repro from my end in my local environment, the below reasons are based on my analysis:
Visual Studio 2022 doesn't include support for the Azure Logic Apps extension. You can refer this MSDocs to check which version is supported for the logic apps extensions.
You can disable and reload the installed azure related extensions and then try launching a logic app in VS code.
And as you mentioned in the question, it may not be ngFork it is ngrok for webhooks extension which you need to install in your vs code. So currently ngrok is needed here as per my analysis and ngrok is mainly used to distribute proxy services to run in any cloud environment but not Ngfork.
Thanking #DEVIN RADER using his blog Configure Windows for Local Webhook Testing Using ngrok for better understanding and as you are using ngrok extension for webhooks, if needed run IIS express which allows http.sys to accept requests from other external sources. To run this, we need to start visual studio as an administrator.
Explicitly tell Windows to allow incoming requests to my ngrok domain by modifying the URL Access Control List (ACL).
When I click on overview logic app from vs code, I am able to get the expected output after checking the above reasons properly:
Right click on logicapp-> click on overview:
Overview of the logic app in VS code:
My workflow sample is also attached:
Right click on logic app -> open in Designer
I go through the below MSDN link to certify custom connector, In that link in the "Step 4: Prepare the connector artifacts" it is given to download files from connector for Power Platform.
As we created Logic Apps Custom Connectors, there is no way mentioned to download files from it.
Link : https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#step-4-prepare-the-connector-artifacts
So does anyone help me out how to download files from Logic Apps Custom connector instead of Power Platform?
You can use Azure CLI instead and follow the same process.
Before running paconn login try installing paconn pip install paconn and then you 'll be directed to sign in using Microsoft's Device Code process.
Then download your custom connector files using paconn download whenafter you've been authenticated.
I developed a test .NET Core Web App to which I added the .doc to .pdf conversion tool GemBox.
Their documentation for Azure deployment combined with .NET Core is limited to non-existing and their support guys could not help me with a clear solution either.
The error I get:
HTTP Error 500.31 - ANCM Failed to Find Native Dependencies Common
solutions to this issue: The specified version of
Microsoft.NetCore.App or Microsoft.AspNetCore.App was not found.
I tracked down the problem to the following issue:
GemBox.Document for .NET Core 3.0 uses WPF.
Is it possible that App Service added a limited support for WPF?
Thanks,
Lorena
The latest released version of GemBox.Document have cross-platform support for saving to PDF which doesn't have a WPF dependency, see the release post or the ASP.NET Core example.
So, you can now use GemBox.Document on Azure services, such as App Service, Azure Functions, etc. without any issue.
I am developing a Windows Forms application with Visual Studio 2013 and i want to publish it in my web site.
I use the VS 2013 publish funcionality using FTP service, it publish it correctly but i see not only a setup.exe is uploaded, but also manifest, and some application carpets...
1.- Is it posible to publish the application under a .msi file?, if so please let me know how.
2.- When i publish it i say to check my page, for example mypage.com, for updates, ¿what should i do in mypage.com when i publish a new version? so when a user is using my app and a new version si avaliable he/she get noticed about it.
sorry for my english and thx in advance.
If you add an installer, you can create a msi.
I used the extension for Vs2013 VSI Bundle.
https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d
The publish functionality I didn't try with that.
See also the Stackoverflow item:
https://stackoverflow.com/a/23339652/200824
I am facing a few problems when trying to integrate the force.com ide with salesforce.com.
Currently i am using eclipse(4.22 Juno) and have installed the plugin Force.com IDE(2.9) and have a developers version in salesforce.com. I was able to successfully connect to salesforce without any errors thru force.com ide, by creating a new application with the name of the application that i have created in the web version.
Right now the application is created with the sub folders classes, triggers etc... but they are empty. I also tried setting the proxy in the connections of eclipse. But even that does not seem to work.
Does anybody have any idea what could be wrong.
Thanks--
Can you post the content of your package.xml file? It's kind of project definition, it contains info which files (objects, classes, pages, reports, profiles...) you want to download & push changes to.
Check http://wiki.developerforce.com/page/An_Introduction_to_Force.com_Metadata for example - have you skipped step similar to this?