I'm using Visual Studio publish to deploy a site using Piranha CMS to a web server. Whenever I deploy the actual image content is lost and I have to upload the image file again to restore it. The database isn't altered during the deployment process, all relations between regions, pages and content remain.
There is nothing in the documentation I can find that covers this, can anyone help?
Related
I'm trying to publish an ASP website with a Azure SQL database to Microsoft Azure using Visual studio 2015 community. Its getting stuck at a certain point and taking too much time. Screen is shown below.
Screenshot of Output window
From the deployment screenshot, it seems your application takes too long time to update file CustomerCarePortal.dll. If this file is too big, it is normal to take some time to upload. If this file is not big, please try to delete this file via ftp, then deploy again to see whether it will reduce your deployment time. You could also try to deploy the application to a new clean Web APP to check whether it related with Azure Web APP environment. If you have some deployment issue, please have a look at this article. The detailed log information may be help to find out the reason.
In my project I'm using Rotativa.dll to generate my PDF reports, it turns out that running the project locally everything works fine, but when I publish my site on Azure WebSites'm not getting. How do I publish an executable file in Azure?
Is there some setting for this?
You can publish any executable you want to an azure site. There is no limitation on the type of assembly you publish.
However there are some APIs that you can't call from an Azure Website for example GDI APIs.
I am not familiar with Rotativa.dll but since you say it's for PDF processing there is a very good chance it's using GDI APIs.
In Dreamweaver I could set up a project such that I had the remote side, where my live site would be located, and the local side, where those same exact files resided on my hard drive with the same structure. How can I do this in Aptana Studio 3.0? I only know how to access a site remotely, so I can edit the files just fine, but I can't figure out how to have a permanent home on my hard drive for the files, so I can (for example) upload new files to my server without opening up a separate FTP program.
On their site, Aptana touts the following as one of the new features of Aptana Studio 2.0:
Radically improved the remotelocal file transfer features. There is an all-new UI and infrastructure for specifying connections, connecting them with projects, and copying files in each direction.
That sounds like what I want to do, but can't figure it out.
There are a few wiki pages on creating connections between a local project and a FTP site:
https://wiki.appcelerator.org/display/tis/FTP%2C+SFTP%2C+and+FTPS+Deployment
https://wiki.appcelerator.org/display/tis/Create+a+FTP+Connection
https://wiki.appcelerator.org/display/tis/Managing+FTP+Connections
Hope these help.
I'm new to both ASP.net and AppHarbor. I also have never deployed an ASP.net application before.
I've set up an MVC4 website using the Visual Studio 2012 release candidate and it is near completion. Locally, it is working fine / as expected.
To send the client a current progress demo, I've been advised that I should use AppHarbor to host the application / website.
I've gone through the process of setting up a Git repository and connecting that with AppHarbor. I then used the Build -> Publish Selection option in Visual Studio to create a 'Web Deploy Package' within my local copy of the repository. Finally, I pushed the files (shown below) that were created to the repository and AppHarbor listed the commit as 'Active'.
However, when I click Go to your application, all I get is this magnificent 403 page.
I've tried a bunch of things (none of which have worked so far) that I've seen in forums (including here and AppHarbor support), including:
Adding a <modules runAllManagedModulesForAllRequests="true"/>
Ensuring I didn't have multiple web projects.
Checking and confirming that there are no errors listed in AppHarbor.
I've turned CustomErrors off, yielding no differences.
I haven't touched any of the .config stuff since I began the project (because I don't know how to use them yet). Perhaps I've just not added something blatantly obvious in there?
You shouldn't use the Web Publish stuff when you want to deploy to AppHarbor. AppHarbor takes your source code straight up, builds it, tests it and deploys it.
Here's a guide on deploying your first app on AppHarbor using Git. There's also a video on the AppHarbor front page that you can check out.
I'm developing a SharePoint 2010 solution which consists of some web parts and other components. Furthermore the solution needs a application pages in the Central Administration for configuration.
So my solution contains an extra feature which places a custom actions in the Central Administration menu that links to a application page providing the configuration. The feature has the scope WebApplication and uses the Attribute AutoActivateInCentralAdmin set to True so the feature is automatically activated in the Central Administration when the solution is deployed to a web application. This part of my solution works as expected.
But I've got some issues regarding the resource files which are used by the application pages in the Central Administration as they only get deployed to the App_GlobalResources folder of web application the solution was deployed to but not to the App_GlobalResources of the Central Administration.
So I'm wondering why to use the AutoActivateInCentralAdmin when there is no automatic deployment of the resource files to the App_GlobalResources folder of Central Administration.
What is the best way to deploy the resource files to the Central Administrations App_GlobalResources folder whenever the solution is deployed to any web application in the farm? Is there an automatic way to this?
We are talking about Application resources here (as opposed to provisioning resources) and they should be deployed to {SharePointRoot}\CONFIG\Resources folder. Make sure the resources files used by your application pages are deployed to that folder when your WSP is deployed.
When a new web application is created, the resources are initially copied to the App_GlobalResources folder, you are fine here.
But when web application is already created (which is your case), you need the resources to be copied to existing web applications. You can do this manually with this command
stsadm –o copyappbincontent
Or you can automate (which is what you want) this by including the following in your FeatureActivated event in your feature receiver. For Central Administration resources and site maps, call
SPWebService.AdministrationService.ApplyApplicationContentToLocalServer();
For regular application page resources and site maps,
SPFarm.Local.Services.GetValue().ApplyApplicationContentToLocalServer();
You need to create a Custom Timer Job for this. If you search on internet, some people have already developed such job.