I am very new for MS Add-in. I followed the instruction to build my first Excel React add-in (ttps://learn.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-quickstart-react). I used Yo generator. I only have Office 365 online. I used "npm run start:web". I didn't make any other changes, except I added the document in config. However, an error showed that "Cannot access manifest ulr at https://127.0.0.1:3000/manifest.xml. Please ensure the url is accessible." I don't know what's wrong. I also tried a Word add-in and same error. Hope somebody can help.
It seems the problem is with your local server if the file can't be accessed directly in any web browser. It is clearly visible the manifest file is not accessible. As soon as you make the file public and reachable in a web browser you may try sideloading your add-in in the Office application.
Related
I am new to Gatsby so please bear with me.
I want to add offline support to my app such that if a user were to try access it while offline (after having visited it online) it would still show up.
Would gatsby-plugin-offline help me achieve this?
If so, how can I try this out? So far I have tried using the plug-in in my app (all default settings), building the app and then serving it locally on my computer at http://localhost:9000/. When I stop the dev server and try access http://localhost:9000/, it does not show up. How can I test to see if this plugin works?
After gatsby build the public folder should include sw.js file.
Otherwise, you can find whether the service worker is registered on not at Chrome Dev Console over Application > Service Workers.
I have been using codenameone to develop an app which I have tested on android, and wish to do so on iOS. I have a paid Apple Developer account, and am able to go through the signing wizard correctly and the "iOS Signing" page is filled out with all of the information.
However, when I come to build an iOS development build, during the ant process the console logs
A certificate from Apple with the appropriate password is required for building an iOS native app!
This is odd, as the information that was filled in was created from the wizard with no errors. On th Apple Developer account page I can see all of the certificates and devices etc...
For some reason, (even when I clicked "browse") when I selected the certificate files it would change the path to my JDK installation
/Library......bin/<selected file>
This is odd, but I ended up fixing it by manually creating the certificates (being unaware of the certificate password.) Trying now, it [the certificate creator] works fine (as long as I change the path once it has finished). It wouldn't allow any full path (IE /Users/....), and would only allow relative paths to the project folder. So when I set the location to the "iosCerts" folder, it worked fine.
iosCerts/<selected file>
This possibly may be an IntelliJ / Mac bug?
I am trying to run BlogEngine.NET. It works fine locally in Visual Studio but whenever I publish it outside of my local computer none of the posts are showing up.
I think this is because none of the scripts or CSS are being loaded (the posts are done via AngularJS). I've made sure that the read and write permissions are allowed in IIS so I know that isn't the problem.
I believe that AngularJS isn't loading properly, as when I go to the admin panel the url returned with the 404 error is this:
8926/admin/%7B%7BSiteVars.RelativeWebRoot%7D%7Dadmin/#/dashboard
instead of:
8926/admin/#/dashboard
Even If I manually take out all of the %7B%7BSiteVars.RelativeWebRoot%7D%7Dadmin text, the posts still don't show up as they do locally which leads me to believe the posts are also tied to AngularJS as well.
Does anyone know how to fix this? This may not be a BlogEngine.NET problem as much as it is just a loading of Javascript and CSS problem inside of IIS
The documentation for my project is here.
BlogEngine.Net had moved to GitHub that is where the latest updates are at.
Best to go here:
https://github.com/rxtur/BlogEngine.NET
and try again with a fresh install.
I have a fresh install working with no issues here:
http://blogengine07.azurewebsites.net
Took a total of around 30 mins to it it 100% up and running, creating new web app service,database, change web.config, publish to Azure, and making some changes in settings.
What web host are you using to host your website?
You can also try Azure Web App Service for free here:
https://azure.microsoft.com/en-us/try/app-service/web/?language=cs
If you can get it to work there but not at your current web host then that points to a web server issue, since you are able to run it locally and on Azure.
Hope this helps.
Have a great Day!
Brian Keith Davis
we are working on a WPF application which we want to publish as a click once smart client application.
We are able to publish the application on local machine using Visual Studio 2012 and configured it in IIS.
Now we want to upload the published smart client installer to windows Azure Virtual Machine with Windows Server 2012 and IIS 8. We cannot upload the locally published components as the URL configuration in the manifest and deployment file is that of local server. We tried to edit the entries using text editor but once we do the editing the files become unused and it shows xml parsing error when we try to install from the location.
we tried to publish the application direct to the Virtual Machine but it shows an error as Front Page Extension is needed in IIS. We tried to find Front Page extension but couldn't find an version for IIS 8 in Windows Server 2012.
Can any one help us to publish the application in Azure Virtual Machine.
The problem you are having has nothing to do with Azure per se.
In the first case (of editing the XML files), you can do that but it's best to use MageUI to do the edit, because you can then re-sign the manifests. If you just edit the files, it messes up the security on them, and they will not work (as you have found). If you want to edit them with a text editor, you can do that, but then you must re-sign them (using mage); you can create a script to change the installation URL.
Or you can use MageUI. You need to do it in this order:
Open the application manifest in the versioned folder and then save it, re-signing it with your signing certificate.
Open the deployment manifest (yourapp.application) in the top deployment folder. Change the Start Folder to be the right Installation URL. Go to the "Application Reference" tab and re-select the application manifest in the versioned folder. (I know, it hasn't changed, but trust me, you have to do this.) Save this manifest and sign it with your signing certificate.
Copy the deployment manifest from the top folder to the versioned folder. It's always good to keep a copy, so you can go backwards a version if you need to.
NOW you can copy the files to your VM and they will work fine.
In the second case, the Front Page Extensions are required if you are using HTTP to publish the application, yet they are no longer available past about Windows Server 2008(?). So don't use HTTP. Use FTP. Set the publish file location using FTP, like ftp://myserver.mycompany.com/myfolder and set the Installation URL to the HTTP equivalent of it. Then publish it. It will put the files on your VM (assuming FTP is enabled on both sides), and the HTTP link should work.
By the way, you can also host your deployment in Azure blob storage. It is dirt cheap, and you can use something like Cerebrata Cloud Storage Studio or even write your own code to publish it (which I did). This article explains how to put the files out there, what the MIME types need to be, etc. If you do this, then it will work even if you need to replace your VM or redeploy it or the VM becomes unavailable for some reason.
here is a reference to Avkash Chauhan's blog post explaining in detail How to deploy ClickOnce Application using Windows Azure Storage in very simple steps?
http://blogs.msdn.com/b/avkashchauhan/archive/2011/05/09/how-to-deploy-clickonce-application-using-windows-azure-storage-in-very-simple-steps.aspx
He also gives an code example of a windows form (using Wpf) that he shows how to deploy on azure using one click deployment.
hope this helps
I have an MVC3 C#.Net web app. I am using the Aspose library to read an Excel file using the WorkBook.LoadData() method. I am able to Load a file from my local machine when running in Visual Studio. I am able to load a file from the web server when running the web site. However, when running the website, I cannot load an Excel file from my local machine. I get the following error
"Unable to open specified Excel Workbook: Could not find a part of the path"
When I grab the path it says it can't fins and use my "Run" command...it finds the file. So, it must be a permissions issue. I am sure there is a simple fix but I don't know what it would be. Any Ideas?
As I suspected, it was a permissions issue. It was not an Aspose issue. I used the MS Interop library to run ImpersonateUser() using a service account that has access to the external machines