Please can some one explain the difference between web project
and web site in visual studio?
I hope to create a new web site for shop which selling mobile
phones.. There should be a admin panel that can be uploaded
new mobile phones and add some banner about special offers in
some season....I hope to build asp.net web site.
User should have ability to sort mobile phones according its
brand name, price ... and also should have filtering facility to find exact phone.
What should I select?
Should I go through web project or web site. Please help me to select
best thing.
Per Ali .Nets response it would be better to create a web application project as opposed to a website.
It totally depends on what you want to do.
Web application and web site is not so different from each other.
Its the technique and function of each other that varies.
If you know how to create website and you want to use it on mobile devices,
functions of it are not a problem, the design does.
There are different bootstrap that can help for your needs like
twitterbootstrap, skeletonUI and many more.
hope it helps.
Related
If we already have a website and web pages(created by VS asp.net) can we able to edit or change or manage these by a new CMS?.
It is highly unlikely. It may be possible to partially accomplish this via a converter tool (something that can parse the .NET site into another CMS) or a scraper tool (something that scrapes the HTML content of the live .NET site and formats it or imports it into a new CMS).
Neither of these, though, if even possible/available, will result in an exact copy of the site in another CMS.
The following screenshot shows what I believe is an ASP.NET website and a web application. Am I correct and which one is which?
(Apologies for maybe duplicate, typed in earlier but can't find it now)
Yes, you are correct. This shows difference between Website and Web application difference.
Left on is Web application while right one is your web site.
Here is link which shows difference between Web site and Web application project in asp.net.
https://msdn.microsoft.com/en-us/library/dd547590(v=vs.110).aspx
Hope this will help you.
Im a little lost here. Im starting on a project for a customer who wants a SaaS solution as a small portal.
The idea is that i make a web solution e.g. an online business card, where each customer should have their own domain like this:
www.carpenter.com
www.painter.com
www.masonry.com
Etc. each of these domains should point to my web application and each have their own administration web site and the online business card. This means that if I go to: www.carpenter.com I should see the companys online business card. And at the url: www.carpenter.com/admin the carpenter company should be able to log in and edit its information.
I hope this makes sense.
What Im looking at is how this is done in practice, I would like to have a central database and a central place to update my software (maybe one per country). What do i need to do to point a www.carpenter.com domain/url to its own specific area in my web app. And how do I need to structure my web application to do this?
Im using ASP.NET MVC for this, but this should be a general question regardless of language - or?
Im considering using a cloud service such as Azure, is this possible with this setup? Or do i need a virtual hosted server i own myself?
I guess the main question is "how do I host multiple domains on the same software" - and keep the display of the "business card" and admin separated from each customer?
Not sure if this specifically answers your question, and my experience thus far has not been with ASP, but I think the general idea is that you determine the execution environment for your web app early in the bootstrap process, and then set constants and configuration options at that point. Then, you can use those values throughout your application to customise the response based on which site you're working with (i.e. carpetner, masonry, etc.). And, since the only piece of differentiating information you have during the bootstrap process is the domain name and URL of the site being requested, I think the generally accepted method is to switch on the domain name. So, you can store different configs for the different sites based on their domain names, and then load those configs during the bootstrap process. For example, if you had a different site template for your carpentry site and your masonry site, you could store the path to your templates as one of the configuration options. HTH
I need some guidance in "best practice" for the following scenario:
I have a product that consists of an ASP.NET website and native smartphone apps for Android/iOS/WP that uses the website URL to call webservices.
We want to move the website from "www.ourdomain.com" to a sub domain like "www.login.ourdomain.com"
This means we're going to update the apps to point to the new URL which isn't a problem.
But as we all know, not all users update their apps instantly, so we want to have a "cross over period" where we run the website on both URLs.
It'll use the same database, but the ASP.NET site code will be altered a bit for the new sub domain site.
Is there any problems in doing this kind of cross over where 2 ASP.NET sites share the same database? (All id's in the db is auto incremented, or GUIDs)
Any help, suggestions or concerns is much appreciated.
I don't see any problem using different service URL for existing mobile apps(Old URL) & updated mobile apps(new URL) and website. I'll call it proxies.
The critical part is regression testing for mobile apps (old one & new one), with the latest change.
It would be great, if deployment fully incorporates the Deployment Workflow.
What I need to do is create a web application that can run inside SharePoint. It needs to be more involved then a web part and include many pages and a database. I know you can create a SharePoint application that goes under the Action bar, but I would like to create something that is run like how a site is. I would want a few tabs to show different sites, each running the same application, just showing their own data.
It looked like creating a site definition would be the best route to achieving this, but I have not been able to get it to become like an ASP.Net Web Application. Anyone know of any other project type or method that can be done to develop an ASP.Net Web Application that simply shows up in SharePoint? I know I can do it in a page viewer webpart, but that just seems like a cheap hack to create an IFrame and not the optimal solution. I don't need any true integration with sharepoint, other then using it for Authentication and a display mechanism. Our corporate intranet is setup using SharePoint, so anything that I build has to exist within it.
If anyone has any guidance, I would love to hear your suggestions.
Thanks!
It's actually pretty straightforward, at the basic level:
Create your ASPX pages with codebehinds in your own assembly - just like normal.
Use the Sharepoint master pages (look at the existing ones to mimic their styles and markup)
Create a Feature which adds a link to your "entry point" page(s) to the SP menu
Deploy your assembly to the GAC