I have an application that I'm trying to publish to my website. The error I'm getting is that when done publishing, it says:
So it looks like it succeeded, but didn't.
My website is located at www.mywebsite.com.
In my build properties, under the publish tab, I click options->deployment, then set deployment webpage title to 'rdl', then I check automatically generate deployment webpage after every publish
I then go through the Publish Wizard:
Specify the location to publish this application: ftp://www.mywebsite.com/
Click next.
Check From a website: Specify the url: http://www.mywebsite.com/
Check Yes, this application will be available online or offline
The final page then states:
The application will be published to:
ftp://www.mywebsite.com/
Users will launch this application from:
http://www.mywebsite.com/
Click Finish
I am then left with the error described in the image above.
When I go to cPanel (my web host), I am able to see the Application Files folder which includes my application folder inside it.My .deploy and .application file are also located there along with any assets I had.
This Application Files folder is on the same level as the public_html folder if that matters.
Any help would be appreciated, I'm not exactly sure where I'm going wrong!
Related
I have downloaded the QAF Maven project and imported into Eclipse. I have created BDD test case for one of the RESTFull service and I am able to run it as TestNG Test. I see the result folder created with the date and timestamp created under test-results folder. When I try to refresh the Dashboard.html I don't see any results and it’s empty.
Please let me know if I have to update my POM or any other property file.
Try opening dashboard.htm in firefox.
You need to open local dashboard.htm in Firfox (prefered), Edge or Safari. If you are opening in chrome you need to set allow file access from file. If dashboard.htm served through http server, for example jenkins then you can open in any browser.
I just put the build folder to the root folder of nginx server, e.g. /var/www/html, but nothing is visible.
When inspect from browser, the root content is empty?
enter image description here
Check your developer console for possible errors. You can also use React Developer Tools to debug your app. You can provide your non-sensitive code to make us understand it better.
I'm building a Node.js app called MouseApp. I notice when editing my app, which puts me in the Bluemix DevOpsServices Web IDE, I cannot see the Bluemix live edit, quick, restart and debug icons. They're just gone.
It does not happen for all apps though, I'm just not sure what distinctions I should be looking at between the 'good' and 'bad' apps.
Does anyone have any ideas as to why my icons are disappearing?
I did some digging and learned that there are a couple of reasons why this happens. All of these are in the context of the app you are editing.
The first cause is if the manifest.yml file is not stored at the top level of the app's project. Putting the manifest.yml file at the project root addresses this.
The second cause is if the app is stored in a subdirectory rather than the top level of the project, but the path to the subdirectory is not specified in the manifest.yml file. This was my cause of my problem. Once I added the path to the subdirectory to my manifest.yml file my icons were back.
path: path_to_MouseApp
The third cause is that the app does not contain a package.json file in the same directory as the app.
When the Live Edit icons are missing, it's because one or more of these problems have happened:
DevOps Services couldn't identify your project as a, well, project.
Fix: Create a project.json file at the root. This should cause some new buttons to appear in the toolbar: Create new launch configuration, Deploy, Stop, etc.
DevOps Services couldn't determine what folder your app lives in.
Fix: As suggested in another answer, you can create a manifest.yml at the root, and edit it so that it points at the app's folder with path: path_to_mouseApp. This will work. Or you can just move the app code into the project root.
After you do this, the Deploy button should become enabled.
DevOps Services thinks your app is not a Node.js app.
Fix: Create a package.json file in the app folder.
Once you've gone through these steps, the Live Edit buttons should appear.
When publish a site in local IIS it shows an exception system cannot find the file specified. But same code work fine in debug mode is there any solution for this.
Read the path from web config file.
Check if the missing file is part of your project in the project explorer. If it is not part of your project, then it will not be published, but it nevertheless may work in debug mode, because the file(s) are locally available.
I have a Win app (VB.net 2005) with an About.htm page that comes up when the user presses F1, using a HelpProvider control.
The application was deployed using ClickOnce technology. When I release a new version I have to manually copy the About.htm file from my development area to our LAN (specified by the HelpNamespace property of the HelpProvider control).
Is there a way I can include this as part of the deployment?
Thank you.
Add the file to your project and set the build action to 'content' and 'copy to output directory' to 'copy always'. Then the file will be included in the deployment when you build and deploy.
To locate it programmatically, assuming you're using winforms (because you're using vs2005), you can find it by looking for it at System.Windows.Forms.Application.StartupPath.
You can open it by doing a Process.Start("iexplore.exe", myHtmlFile). You could also make a form and show the about file in a web browser control pointing to the file as a URI.
RobinDotNet
I think the best way is to make your Help-File a part of the Application. Take a look at this question. With this way the Help-File will be downloaded with your Click-Once application.