Kindly find the below doubt and do his needful on the earliest of tomorrow..... Thx and can I have an urgent
Make a simple Web form for registration of students and courses. The form should accept first name, last name, faculty number, university (drop-down list), specialty (drop-down list) and a list of courses (multi-select list). Use the appropriate Web server controls. After registration you should display summary of the entered information as formatted HTML. use dynamically generated tags (h1, p, …).
1) We do not do your homework: it is set for a reason. It is there so that you think about what you have been told, and try to understand it. It is also there so that your tutor can identify areas where you are weak, and focus more attention on remedial action.
Try it yourself, you may find it is not as difficult as you think!
2) Wrong location - try posting questions in appropriate forum or on QA - but don't expect an answer in it's present form. See (1) above.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
by choice, I would avoid the Metro UI for the sake of my sanity.
Panic, Chaos, Destruction. My work here is done.
Drink. Get drunk. Fall over - P O'H
OK, I will win to day or my name isn't Ethel Crudacre! - DDEthel Crudacre
I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer
Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
As enterprise developers, I felt migration from Winform to WPF and socket to WCF been a complete waste of time - what is it that it can be done in WPF/WCF that you can't do with simple Winform/socket? Bit sick of ideological changes which don't offer quantum leap in real capability.
I know what you mean but I think there's a couple of differences.
With WPF you shift the bulk of the rendering work to the GPU, customers seem to want more UI glitz in their apps at the moment, and getting shadows, reflects and all that out of GDI is pushing it further than it was ever designed to go. Using WPF puts the strain of that on the GPU and leaves the CPU free to work on the logic which is a nice idea.
WCF isn't a ground-breaking change over sockets if you're using a TCP/IP communication protocol, but it does allow you to build services that work over HTTP, or message queues, or pipes and so on, without having to redesign low-level code, so it is quite useful at abstracting the technicalities of a communications protocol. Also, if you have a sockets app that has two-way communication and have (again as a customer requirement) to then expose it over HTML, with WCF you can create a duplex service that actually runs over HTTP, which is really nice.
I think the key thing for me is that they haven't given either of these systems enough time to mature yet - for us in house it's only with the latest versions that WPF and WCF are really usable choices - we're starting to see developers do some really nice stuff with them, but suddenly are we going to be forced to drop it and learn something new?
I'm playing devil's advocate here though because frankly I want them to reinvest in C++/MFC because so many of us still use it:
I'd really like to see a survey of what big apps written in Visual Studio use - C++/C#/Basic, MFC/Win32/WPF/WinForms, ASP.NET/Silverlight etc - it would be better for customers for MS to focus on the most well used technologies, as well as attempting to improve on them.
I have one WP7 app in the marketplace, I built it as a side project, and I learned a lot putting it together. I'm currently working on another app for WP7, and have an idea for a third. I'm building them in a nice MVVM way that should allow me to just replace the View so it scales to a full size screen with little or no changes to the View Model or Model*. I will definitely be putting those into the Windows 8 marketplace before the initial release.
*Actually I'm making use of the new Portable Class Library project, so I should need to make any changes to the View Model or the Model for my second app. I'm only in the thought phase of the 3rd idea, and that might require something that the PCL doesn't support, so I might need some custom dll's for each environment for that.
Ok, not really, but it's more than I expected. I first released Chess Tactics[^](<-shameless plug) on 4/22, so it's only been out for 12 days. It's free, and I've had a lot more downloads than I expected ~900 through 4/27 (MS Downloads reporting runs days late). I'm using Microsoft's ad control, and so far that has brought in about $12.
While that averages out to $1/day, I doubt I will see >$300 annually. The first few days saw a pretty larger numbers of downloads, and larger numbers of ad impressions (and higher payment per impression, but I think that's just luck). The last two days for which I have a full days number have earned less than $.50.
I'm not discouraged at all though. I'm putting an update out soon to improve the UI, and to fix a bug in the ad control that crashes the app at a time the user would never notice (if you launch the app, then close it before the ad control receives it's first ad).
I've also started on another project that expect to make even less money. It may not be good business sense, but it's fun
How does the ad control work? Pure click based or is there something else it it?
I have a few ideas but don't think I can 'charge' out the gate for them, but want some kind of revenue for making the apps.
May not generate alot but if you enjoy it that is great. Also maybe you will get a stellar idea and impliment and have the next "instagram"
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
That ad control is simple to implement. Download the control (I think it comes with the WP7 SDK now). Sign up at pubcenter.microsoft.com. Drag the add control onto the form, set two properties and you're ready to go (the bug that was crashing my app is fixed in the latest release of the ad control).
It pays per impression, and from what I've read the click through rate doesn't affect the price. Advertiser bid on the space based on categories and keywords, so you never know what you're going to get from day to day. I've received as much as ~$2.50/1000 impressions to as little as ~$.50/1000 impressions.
Maybe someday I'll find an idea that pays, until then it's just scratching an itch my day job can't.
There used to be a lot of polemic about what is better and etc.
Metro vs Desktop is the same. Each has its own place and use.
Just get over it. It is here to stay and most of us will end up developing for it.
It is here to stay and most of us will end up developing for it.
Agree... the market is the market, and 95% of the world doesn't give a sh*t on the reasons we can have or point out to try to avoid it.
The only ones that might avoid it are the ones that get in retired in the next one or two years. The rest of us... close the mouth, swallow it down and learn the new tendence.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
I don't plan to retire yet, but I do see alternatives. Frameworks, libraries and operating system versions come and go. There is no need to keep up with all that. Algorithms and architechture usually are independent of programming languages and frameworks. Those are the things to concentrate on and then learning to use some currently popular thing will be no effort. And they will also be forgotten just as quickly.
My personal alternative will be to leave the nice orderly .Net world and look for a nice C++ job. Somebody has to work on those nice operating systems, drivers or GUIs. And I have gotten tired of playing with Lego. Time to write some real code again.
At least artificial intelligence already is superior to natural stupidity
The problem is, Microsoft really shouldn't have called it "Windows 8" - it should really be called "Windows Tablet 1.0" or "Windows Touch 1.0" to distinguish this from traditional "desktop" Windows.
I think, in future,
"Tablet" is for everything read only (or not to much typing)
"Desktop" is for serious work or server side
There's no advantage for a mechnical engineer to start assembling CAD drawing on Windows 8 for instance. Similarly, I don't think developers will start do serious coding in (not coding for) Windows 8 environment. In general, anything/work which requires a couple screens and a lot of typing is unsuitable for tablet styled environment.
The problem is, Microsoft really shouldn't have called it "Windows 8" - it
should really be called "Windows Tablet 1.0"
Indeed. I don't see myself using touchscreens (they should better have been called smearscreens) or stamp sized displays on desktop computers. That makes me totally unwilling to deal with other devices' shortcomings on a desktop machine just because they had to put everything in one bag.
At least artificial intelligence already is superior to natural stupidity