Alright, I am obviously missing something here. I have moved several websites over to Azure to take advantage of all that it has to offer. Traditionally our team has always used DreamWeaver to ftp up/down and such. What I don't understand is how I go about getting hooked up to an EXISTING site on Azure. I can easily setup and web deploy to a NEW site, but I am trying to give the rest of the team access to the sites I have setup and I am lost as to how to approach this.
I have tried the File > Open Web Site route, and the issue with that is it never then saves the project/info anywhere in VS, and we are required to hook back up to it each time.
All of our local sites are on a shared network drive, so we all access the same local resources. I thought I could simply pass them all the publish profiles and they could then import, get, and then edit and publish files... but it never gives the option to "get all files" from the server.
Hope this makes sense?! Thanks in advance! :)
For multiple developer scenarios, it would be in your best interest to use a source control system such as Git or TFS. This will allow you not only to share the source across team members, but also give you the benefit of tracking changes and merging files that are modified across team members.
If you aren't comfortable with source control, you do still have access to the files via FTP or Secure FTP.
You could also use WebMatrix which has the concept of download from server built directly into the tooling.
Related
I'm wondering if my website need to be hosted on a different server for load balancing purposes as picture below:
I'm thinking of installing 3 Kentico Project into each server. Then, export and import the site into each Kentico Project and link with the same database connection string.
But what if one of the webparts (.ascx) gets updated? Is that mean I will need to update all 3 Kentico Project. What if other files like js, css, or media?
Is there a proper way to host on different servers but yet can manage the content as one of the Kentico Project get update?
What you are describing is the exact purpose of Kentico's Web farm feature where you can have multiple servers (web farms) connected to a single database. The main purpose of web farms is to ensure that cache and files (not code files, but media files such as the ones uploaded by you as attachments, media library, meta files...) are synchronized across all servers.
Each server in your scenario has its own memory and if you change an object, you want all other servers to reflect the change because otherwise some visitors might end up seeing "old" data, while others wouldn't.
You are also correct in assumption that all code files (ascx, cs, aspx...) will need to be uploaded to all servers. Best way to approach this is to have a tool such as Team city which is able to deploy your changes to multiple servers simultaneously.
With js, css, html, images... it depends where you store them. If you store them in database (not usually the best thing to do) you don't need to update them on particular servers, but if you store them on file system, you might need to. There are many variables here, but some deployment tool will probably be the best bet.
One note here. Try not to install Kentico directly on each of those server and use Export and Import to setup the site. Simply make a copy of the website physically files from your DEV server and paste into each of those server. Then connect them all to the same database.
Why not use the Export and Import? 1. You will get different hast salt string in the web.config which you will get Macro security error, which you will have to replace with the same key. 2. You may miss objects during export and import. 3. The export and import are mostly for the objects stored in the data base, and for the web farm setup, they share the same database, so there is no point of doing that.
You can easily achieve this move to windows Azure from on-premises.
--Can deploy your website/ web project as Cloud service/App service.
--Kentico Azure supports both development and deployment solution
--Built-in scalability
For more details refer below links
Hosting options: https://docs.kentico.com/k10/running-kentico-on-microsoft-azure/microsoft-azure-web-hosting-options
https://devnet.kentico.com/articles/deploying-kentico-to-microsoft-azure-know-your-web-hosting-options
I have 2 azure websites in the same subscription and I want to copy the site from one to another. I know I can copy the entire site down to my local machine using FTP then upload the entire site, but it seems like there should be an easier way, especially considering the FTP hostname is the same for both sites.
These are not deployment slots, so I can't just swap them in the interface.
Thanks.
I think you can use the SiteReplicator site extension to do that. You can find it here https://www.siteextensions.net/packages/sitereplicator/.
The scm site can be found at URL_OF_Your_SITE.scm.azurewebsites.net and then go to Site Extensions to install it if it's not visible in the portal under the Site Extensions gallery.
You can use backup/restore feature. That will create a ZIP file from your site, store it in your storage account (including configuration serialized to XML) and then you can restore to a different/new site. In the end it is basically copying files around anyway, but maybe it is fancier than doing it manually through FTP. Another benefit is that also the website's configuration is copied around. This is one time thing only though. It is not clear from your question whether you want to do copy one time or periodically (that I would suggest the site replicator mentioned in the other response here).
Some links which might help:
Backup - http://azure.microsoft.com/en-us/documentation/articles/web-sites-backup/
Restore - http://azure.microsoft.com/en-us/documentation/articles/web-sites-restore/
its my first time using this and as a newbie I have many questions. Any help are appreciated.
My ultimate goal is to have reports created from database that will be able to be accessed by other end users on website so they can view/filter the report data online in a shared way with some user control settings.
So I have already made my reports in the visual studio linking to databases.
And I have also set up the Reporting Service Configuration Manager so that I can access SSRS home page and the site setting at http://'127.0.0.1'/Reports/Pages/Folder.aspx
Now my question is, how will the other end users be able to get onto the website and get access to the reports I created with SSRS? Do I upload the reports in .rdl on my report site manually or do I deploy it from VS? How do I turn my '127.0.0.1/Reports' into a public site for other user's access? Or do I have to create it using a sharepoint?
Thanks so much, I need a guidance to head toward the right direction! :)
Now my question is, how will the other end users be able to get onto the website and get access to the reports I created with SSRS?
Users will need 2 things from you to access the site: the server name/address, and a means of authenticating to it. By default, authentication is handle via Windows domain auth (which you can change, with varying degrees of effort...).
Do I upload the reports in .rdl on my report site manually or do I deploy it from VS?
It actually makes no difference in the end; do whichever you find easier. (There are also plenty of other ways to deploy reports, such as through powershell!)
How do I turn my '127.0.0.1/Reports' into a public site for other user's access?
Well you're halfway there - At this point, you could probably open up your firewall (port 80, maybe 443 depending on your config), and have people connect to your computer via IP or hostname - for example, if your computer's IP was 12.34.56.78, they could visit 12.34.56.78/Reports/ and access the site. If you have a means of creating a URL and pointing it to your SSRS server, you might need to open the configuration manager again and bind that URL to SSRS.
My company has a shared network folder for projects. This folder contains a sub-folder for each of our clients. Each sub-folder contains all the information for the projects done for those clients. Makes sense, yea?
OK.
I have been given a task: When in our company's MS CRM and viewing a client account, allow the user to click a button that will open explorer to the project folder for that account.
Sounds easy.
Did a bit of hunting online. This looks nice: http://blogs.msdn.com/crm/archive/2007/04/18/integrating-windows-explorer-files-and-folders-into-crm-tabs.aspx
It's funky, but it goes waaay beyond the scope of the task I've actually been given. However, my company doesn't use SharePoint (though we have licenses if we need it) and I don't have the time to invest tweaking this solution until it fits our CRM. I just need to open explorer on the client machine and point it at a folder. I want a button that will open explorer. Should be easy! I just want to set up a button in CRM, execute the command to open explorer /root, //server/projects/account, and then move on to more important things.
That said, I don't think like a hacker, so I didn't realize that this was an obvious security exploit that will be blocked most (if not all) of the time. So I gave it a go, but I've been having trouble opening explorer with JavaScript, which I thought would be the quick, easy and painless solution (duh me!)
Is there an easier way to do this than the example I cited above?
Actually if you direct Internet Explorer to a local protocol, network shared folder or ftp server it turns to a file browser. This is automatic and you dont need to do anything other than making the folder you talk about to a network shared folder (via SMB) or FTP server. Just open that address in a new window:
window.open("file://\\192.168.1.10\clients\112");
window.open("ftp://192.168.1.10/clients/112");
either one should work
I'm in the process of moving a complete sharepoint install to a different server.
Can anyone tell me if it's possible to just move the existing Shared Services Provider rather than starting from scratch?
All the best
You really need to move the SSP in concert with everything else in the farm. The two things to move are 1. databases and 2. the file system.
A .doc file for moving all of the SharePoint databases has been published here. Microsoft will soon have an updated procedure for this published on TechNet, according to the To The SharePoint blog.
Then to cover off any file system changes, I would set up a clean install of SharePoint (if you didn't need to already by following the document mentioned above) and do a file comparison between your source and destination SharePoint application servers. I usually use WinMerge as its free but Beyond Compare is also good. Also check any custom solutions are deployed on your destination server.
By ensuring your databases are moved correctly and all of your files are in place you should be OK. Make sure you test every custom component on your destination server before erasing the source databases and files (even better, archive the source).
Yes, create a new SSP and move the applications.
How to on migration of applications here
For moving the SSP to a new farm
Or try the Microsoft SharePoint Administration ToolKit v2.0
For another view of this