We have developed an desktop educational software using WPF/C# technology. The software will be used by School teachers and Parents. We are planning to make a web and mobile version of it. We have limited experience in web development. Some of the team members have limited knowledge on ASP.Net and I do not have experience in web technologies. I am evaluating the best platform to develop the web version of the application.
Looking at the trend, I see below technologies available.
1- Silverlight: Easier as we have experience in WPF. However, put limitation to install silverlight on the machine. Also, seems future of it not bright.
2. ASP.Net MVC5: might be useful as we are aware of the .Net/C#. Read that it's not the best for multiple browsers.
3. ASP.Net MVC5 + HTML5/CSS: Latest technology and provides nice webpage.
I am bit confused between a ASP.Net MVC5 and (ASP.net MVC5 + HTML5/CSS). Both the technologies are new to me and I have to learn and develop. I am more inclined towards (ASP.net MVC5 + HTML5/CSS) as it is the latest.
Looking forward to your views and also let me know if there is something better for a novice web developer.
I want to develop webpages using dotnet with oracle database. Is there any utility available for generating .net program using a table/tables from oracle ? One or two oracle tables may be joined using a condition or a join can be used.
ADO.NET supports Oracle databases already and LINQ is very useful at several levels of abstraction -- DataSets/DataTables/XML/etc. Oracle probably has a console for DB administration, but I do not use Oracle -- but there is an Oracle Provider native to the .NET system.
Can anyone tell me what price range can i expect to pay for a website that features an email list (people sign in) and a donation button, thus it is able to take payments. Also, what is the specific skills, experience, and knowledge I should look for in a developer?
A basic ASP.NET website will suffice for the generalized specification you are describing -- in fact, even a plain vanilla HTML server can achieve that with little difficulty. My site and domain run about $100/year and it includes 1 SQL Server database and also unlimited mySQL and Access databases and some decent amount of storage. It is not at all difficult for me to write all the code, do all of the ftp for updates, configure .NET, the DB and even the e-mail is simple to maintain.
Starting at the beginning:
1. e-mail -- This is a benefit of two things...first, buy a domain name -- it is your site's 'space' and has the authority to generate e-mail addresses -- it is intrinsic to the domain. Second, your POP3 and/or IMAP and SMTP servers will be at your host's site, usually. So, get that domain hosted -- then you will have a domain and all the rights and benefits of that. Most hosting is one-stop -- you get your domain name, hosting and database from one place.
2. ASP.NET has a preference for SQL Server -- makes sense -- they are both Microsoft technologies. It should come as no great surprise then that there exists a command line tool to generate a SQL database for use with ASP.NET that includes tables for Applications, Users, Profiles...etc. It is the basic database that ASP.NET supports seamlessly and essentially automatically. I know that many developers do not even know that this tools exists, but -- it does and it works quite well for creating a basic database that is already connected to much of the code needed to operate the Membership.
So...you are not asking for a lot, but I would recommend that you take some time to understand the major 'bullet points' with respect to HTTP and HTTPS. Everything else is built on that and most issues with websites are either poor design, poor implementation or a violation of HTTP rules.
There are some basic tools that most of us use -- Fiddler is one of the best that is still free and it can see -- pretty much everything -- the client and server interaction and it already understands the protocols used, regardless of the delivery vehicle. Browsers also have a decent complement of developer tools in them already. That part is your developer's preference and skill set. Some people do not care for ASP.NET and use Apache for their server's home, for example. They all must comply with the rules of HTTP/HTTPS --- they are protocols -- rules for communications.
In my case, my host has a Control Panel where I update the sites I maintain, the e-mail, any SSL Certificates I use and basically manage the site/domain. Most developers I know work at places that either maintain their own domain, or have one hosted site. I use WinHost's Control Panel, Microsoft SQL Server Management Studio and Visual Studio.
Personally, if I wanted one developer to manage all of that -- I would be very keen to find someone that was technically competent in all of these aspects, but -- most places have those responsibilities spread across a few people to several departments -- there is quite a bit to get absolutely correct, as I am sure you are aware. Not a big deal to small fish, but you are asking for something that -- at the Enterprise level spans a few departments.
Take heart, though. It is not so huge and daunting to everyone and you know -- you must trust the people that provide the parts that you cannot and probably, you already have a process for learning to trust someone -- I would use that. One last thing -- this site you are describing -- has already been written thosands of times -- the paradigm -- is ubiquitous. Beware of a developer that will simply steal someone else's exemplar and pass it off to you as theirs. There is -- alot of that going on and ultimately, whoever the domain lists as the cognizant authorities are responsible for the site and its content.
Nice summary - I would only add that there is no need to separate out using SQL Server with ASP.NET/IIS and MySQL with PHP/Apache, as MySQL can work perfectly well with ASP.NET on a Windows server. An advantage of using MySQL is that it is easier to find (even) cheaper hosting options using it.
I want to develop a website for a shoe manufacture with the following support
1) Display the items based on categories
2) Item details
3) Login for retailers
4) online shopping support in future
5) It should work on all web browsers and its versions (ie5 to ie10, chrome, firefox(all version), safari(all version) etc)
6) Mobile platform (android, ios, etc)
7) iPad and notepads
Please help to chose the right technology which will be the best and easy to develop and maintain the web site? which also fulfills the above requirement
Technologies in my mind, but not sure which one to use
1) HTML & CSS
8) Which DB to use
please let me know if i have missed other technologies
5) It should work on all web browsers and its versions (ie5 to ie10, chrome, firefox(all version), safari(all version) etc)
IE5?! You want to support a browser that was released 14 years ago, which has absolutely no support for modern standards? You'll struggle to even find a computer that will run it these days.
You'll have the same problem with supporting all versions of Firefox, Safari, etc. - they're so old that they don't support modern standards.
The only way to ensure that your site will work properly in all old browsers is to stick to extremely basic pages, with no script and no fancy layout. As soon as you start trying to make it look pretty, you can guarantee that it won't work as expected in at least one old browser version.
Trying to support all old versions of all browsers is an unrealistic goal. Unless you have specific data that shows your customers will be using anything else, you should only worry about the last two or three versions of the main browsers. The only time you'll typically encounter older versions is if your customers are using Firefox ESR[^], are stuck on Windows XP (which doesn't support anything later than IE8), or have a corporate policy which prevents them from upgrading IE.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Your question --- has little guidance for answering it properly and -- although it might seem to you that is is easily answerable -- it does not contain enough information for us to help you and it appears that you are wanting widespead browser support -- that is a self-defeating goal when you go that far back.
You appear to be at the very beginning of the process -- so that explains your post to me enough that I can recommend some things that should help you along the way.
You are developing a site for a shoe maufacturer -- let's start with that. What aspects of the business will the site be responsible for implementing? Production? Inventory? Worker hours/pay/training/evaluation? Will the administrative staff want to use it? Will it have eCommerce? A catalog? Buyer information? Vendors?
As you can see -- what you need to use depends on what you seek from the code...so -- be detailed about what you expect and where you want to go with it. You will undoubtedly get tripped up if you fail to mention some major functionality and start in a direction that will not support that functionality. It is very difficult to implement major functionality and integrate that into the system after the fact. Engineering is a far more demanding discipline than many developers know and a system that is 'shot from the hip' will not make it to the end of the SDLC intact -- no amount of managerial voodoo will fix poor engineering -- not Agile -- not anything.
Besides, there are many developers and lots of documentation already and also -- Microsoft implements most of the technologies you will need either 'out of the box' or through 3rd party resources -- it makes sense for a would-be tool provider to support Microsoft technologies -- right?
As for supporting ancient browsers -- the server can be made to accomodate whatever browser is requesting a page, for example -- the real question is -- is that a cost effective answer and have you looked at your potential user base and noticed a need, or are you simply wanting to cover all contingencies? Either way -- as has already been said -- those browsers are museum pieces at this point -- but that is the client side and again -- the server can be made to accomodate those browsers -- but, the functionality would of course suffer. So -- if you know that some of your users have only IE5 and are willing to live with that -- certainly it would be very noble of you to support that...but you would be gaining little -- apart from someone's appreciation. How much is that worth to you? Is it worth thousands of dollars of development time and effort and potential issues? I would think that someone that is still insisting on using IE5 probably has not bought shoes in -- years, and they will not be buying any on your eCommerce site using IE5....just a fact, my friend. I doubt tht you will see much of that though -- so my advice to you is not to worry about IE before 7 or 8. Honestly -- I use IE9 and it is more of a nightmare and hinderance to me than 7 or 8 were. 10 and 11 are promised to be better, but -- I have not seen that to be true for me so far. Truth is -- I miss 8 and Chrome is more developer friendly to me.
Aye...I do not envy you at all here. Some things that might be going on and to help you get a 'handle' on this...
The StringWriter -- make sure it is UTF-8 and about Firefox -- when all you have been told is that an encoding is Unicode -- it is usually UTF-16 by default (At least that is the case for VisualStudio here in the US, perhaps for FF it is UTF-8, but who knows? Maybe look deeper in the settings for FF to see if it is specified somewhere.) For example I have encountered a case where a TextWriter defaults to UTF-16 and you have to make that UTF-8 if you want to write valid XML for a schema that is already UTF-8. The class that your StringWriter is derived from might need to be coerced to be UTF-8, for example.
Could there be BOMs in the text? What are the NUMERIC values of the bytes in that string? BOMs in documents usually get interpreted as strange sequences, like this one: ï»¿ . The values for a BOM would be 0xef 0xbb 0xbf and they would be the first 3 bytes of a document.
Java uses modified UTF-8 for some things (object serialization and literal strings in classes) and was that string serialized using Java? If so, it is not UTF-8 -- it is modified UTF-8. Modified UTF-8 does not use 0x00 as the null terminator -- it uses 0xc0 0x80. UTF-8 can be guaranteed by using an OutputStreamWriter for serialization into your request stream.