There are many ideas that you can use to get a subject for your final year project. In ASP.NET, you can select to create a Web API solution to provide solutions to cross-platform devices, Android, Windows Phone and other similar devices. You can also show your teachers how you managed the HTTP communication, in which data-interchange language (XML or JSON) and other similar stuff.
But final steps are onto you, you have to build the project and that is why you should consider your own final year project based on your own skill sets so that you can present the projects too.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
A pub quiz site that can be hosted on a local server and interface to mobile devices for the teams.
The software will deliver multi-choice questions.
You could throw in added features like difficulty scores and the options provided in Who Wants to Be a Millionaire. Timed questions. Keeping track of questions already presented to teams or individuals.
Consider administrative functions like adding or uploading more questions. League tables for teams and individuals, or a knockout tournament.
For even more challenge throw in pictures, video, audio or interactive content. The questions themselves might be mini-games or puzzles, such as code breaking or solving a Sudoku grid.
It's your call how much of the above you include. If you collaborate, make sure you document the over all design and the interfaces between you and your team mates work BEFORE you all go off and cut code. In the real world you'd whiteboard and discuss designs within a team and then someone would document.
I read all articles about these differents solutions and I already implemented and tested them. I don't know wich one to choose between solution 1 and solution 2. Is there an history or performance or architecture maintenance reason that explain a solution is better than another. Are DelegatingHandler and/or ActionFilterAttribute a old feature?
If you want to log every request, then use the IIS log. That will include requests which might not be mapped to the Web API pipeline, and therefore wouldn't be picked up by a DelegatingHandler or action filter.
If you just want to log the Web API requests, then either a DelegatingHandler or an action filter will work. Neither is an "old" feature. However, if you want to log the request and response bodies as a single entry, the DelegatingHandler would be the better choice.
I am an experienced programmer but very new to ASP.NET. I am needing to code a simple web app and unsure of the best way to do it. I know how to find most answers on my own, so I won't be a needy person here. I just need to know the general design I should follow.
The web app is for a company that needs employees to enter data into a time log excel spreadsheet. My design simplifies the process using a step-by-step method that prompts for each item (i.e. start time, activity type). As the user inputs data, the answers are fed into the excel spd using COM (don't need any help there).
An example of the process:
1. Select your name (from DDL - I plan to automate this by login)
2. Enter your hours
The data inputted is contextual. In other words, what is prompted for in #4 can be dependent upon #1. This means the Server must keep up with all the information until the entry is complete.
Sorry if this is TMI. The short of it is, how do I display each step? Should they all be separate web pages? My gut says that's a bad idea. Is there a way to stay on one page and enter all this data one at a time? Currently I'm working with a Windows Forms ASP.NET web project.
Bonus points: The windows app I coded is smart enough to dynamically create the prompts, and it would be *amazing* if the web app could do the same.
From a UI standpoint you can generally do with a web app the things that you can do with a native one as long as you consider the limitations of the sandbox (you won't be hooking graphics hardware directly, etc). I've found that for enterprise applications that doens't matter much.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
Also added this code on Page_Init() for master page
If Session("culture") IsNothingThen
Session("culture") = HttpContext.Current.Request.UserLanguages(0)
also for the controls it is like this
and i added App_LocalResources with 2 files for everypage(one for en and other for ar)
when i click on change language button it works but when move into other view within multiview inside same page language change back into user browser default language, so i have to click on change language button again to change the language
Can someone tell me what wrong with my code
P.S.: I tried with cookies same result
i solved by using Global.asax and moved setting culture code into Application_OnAcquireRequestState event
modified 5-Oct-16 6:54am.
Last Visit: 31-Dec-99 18:00 Last Update: 11-Apr-21 18:54