I am very new in ASP.NET. Actually I code in vb.net and trying to make a database driven dynamic website.
I use to connect database through an XML file where I put the server, database name, user id and password. Then from a class I call these to connect the database. In this class I put the connectionstring which always read the data from the XML file like...
If (IO.File.Exists("db.xml")) ThenDim DbXmlReader As XmlReader = New XmlTextReader("db.xml")
Dim DbNodeType = DbXmlReader.NodeType
If (DbNodeType = XmlNodeType.Element) ThenIf (DbXmlReader.Name = "server") Then
srv = DbXmlReader.ReadInnerXml.ToString
the above code is just a snippet.
Now my questions are...
1. Is the above method possible in ASP.NET to connect with a database ?
2. If not, then how should I connect with the database ?
3. Lastly, is there any good tutorial for beginners that how to create a database driven dynamic website from scratch in ASP.NET?
The tutorial should have all like add a template, adding css, database connection etc.
For more examples of connection strings, see:
Dim connectionStringSettings As ConnectionStringSettings = ConfigurationManager.ConnectionStrings("MyConnectionString")
Using connection AsNew SqlConnection(connectionStringSettings.ConnectionString)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
if you are saying that you have a web application and a user open your web site on a mobile browser - and you want to track that user - then, you can follow the following:
- each request to your page from any browser will have headers associated with them which will tell you which device is the request from.
- you can use this 51degrees api to detect the mobile devices - http://51degrees.codeplex.com/[^]
- once you detect the device - you can perform your business logic
In a small company, I am making small changes to a vb.net web forms 2010 application. There are no pervious directions on how toset up the deployment of the application. I have used the old version of deployment using msi packages that are not supported after asp.net 2010. I have not used web deployment yet. I set attached to this application that there is a web deployment project that was used.
Thus can you give me directions and/or point me to a url that will tell me how to setup a web deployment project that can be installed on an IIS server.
I don't think anybody uses web deployment any more, but I haven't taken a poll on the question.
That was a Server 2003 Thing, and IIS6 using meta compatibility or something. I don't remember anymore, but it was another one of those Microsoft things in which they tried to make ASP.NET / Server 2003 look more appealing by offering the deployment program, and then phased it out later on down the road.
I used it back in 2004/2007, then phased it out in 2008 when server 2008 was released. That was 6 years ago.
Speaking of IIS servers, IIS has come a long ways since IIS 5.5 and 6.0
Setting up a web site using web deployment on server 2008+ is a huge security risk.
Times have changed, server 2012 using hyper-visors and virtual servers are the in thing today.
Just copy the folder to the web server, and use the IIS Management console to setup a test website, and play around with it. Don't forget to set your folder permissions for the application pool user, set your bindings and you should be OK. If you need to write to the drive, set the trust level.
DISCLOSURE: I am not a web developer, but I've heard a lot of buzz words about web development
I have a client with small data needs for some very confidential information for his clients, which number around 3,500. For the past 20 years we have done everything on a small server located on-premises, to which only a handful of people have access. Much of the information we have been getting and storing has come from paper forms the clients complete and send in by snail mail, whereupon the data is keyed in to our WPF-based/SQL Server-backed system.
Times change and we now find it necessary to give his clients access to their own information via the web. They'll also be expected to provide updates via the web, rather than the paper forms of old. My client is paranoid about public web hosting and the thought of letting his data go off-site, but DOES NOT have the ability and/or resources to administer a web site locally on his own server.
So, down to the questions:
How feasible is it to use a public host for a web site to handle all the login/authorization stuff, and have that site retrieve the data from, and update the data on, our on-premises server?
How does one manage the tasks of 1) setting up several thousand users with secure login credentials, and 2) managing account lockouts/forgotten passwords/etc.?
What technologies would you advise using? ASP.Net & Azure, for example? What about SharePoint? Non-MS technologies?
What important questions am I not asking here?
Perhaps the biggest question: What important questions do I need to ask my client?
Your going to need a couple of decent web servers like a Dell T110 II to design your system on, build your web app and test it. There pretty cheap to acquire, and have nice speed, but it is up to date for current OS and supports virtualization and AES Encryption for SSL. Or one heck of a workstation like a 6 core Xeon to develop on, and build your virtual machines.
We have test servers in house that we spent months on for the design. We created a design in which we can just copy the stuff to a Public Web Hosting facility that supports our design.
So we went with server 2012 standard, created a hyper-visor server core, and created 3 virtual machines using server core, no GUI and partial GUI. One virtual runs the database server, the other the web server, and a backup server.
You can use VMWare in which I like, or the stock Hyper-V virtual machines. Once you dial in your virtual machine, you can copy the machine like a file copy, and upload the machine to a public web hosting facility.
So for the Public Hosting, we choose our internet provider, that has facilities in Las Vegas and Texas, in which they run blade servers with Hyper-V or VMWare. So we get a firewall, a blade server, and access to let's say 6 virtual machines that we can upload. So we upload and download virtual machines, back them up every couple of hours using something like Veeam, and can restore them in minutes if needed.
Regardless of what technology you choose, I think this is the way to go for 2014 and is the current way of the future.
I'm not that worried about being hacked by the neighbor, because you can really fine tune the firewall in server 2012, and limit access to domain members only.
Thanks for taking the time to explain your design and thought process. What isn't clear to me is whether you're putting the db server on the public host or keeping that local. If local, how responsive is you overall set up?
Also, how did you, or how would you, manage the tasks of setting up and administering all the logins?
Last Visit: 31-Dec-99 18:00 Last Update: 31-Jul-14 12:13