Porting .NET To MVC.NET - Storing SiteConfiguration In Cache RESTful?
Apr 26, 2010
I've been tasked with porting/refactoring a Web Application Platform that we have from ASP.NET to MVC.NET. Ideally I could use all the existing platform's configurations to determine the properties of the site that is presented.Is it RESTful to keep a SiteConfiguration object which contains all of our various page configuration data in the System.Web.Caching.Cache? There are a lot of settings that need to be loaded when the user acceses our site so it's inefficient for each user to have to load the same settings every time they access.
Since I don't want my sessions to be removed unless the session has been abandoned either via code or Session Timeout...For eviction, I would think "None" and for expireable, I would think False.I have tested and calling Session.Abandon does remove the object from the cache. I have also tested to see if by extending my session, the session object in cache is also extended. This does seem to work the "correct" way.
I know i can store a string in the cache, but can I save a date in cache and retreive it back into a data variable without having to convert.todatetime.
I am writing a web page that returns a small volume of data from a database table. The database is polled every 1 second and the data will be the same for every user. As every user is accessing the same data, there is no need for each user to poll the database and use up db resource.
Therefore, I think I should be using application caching to store the data in a dataset. However, I am slightly stumped as to how to do this.... because how can i ensure that the dataset is kept up to date.
The only way I can think to do this is to have a master user/session (i.e. the first session in the application) that keeps the cache object updated every second, then other users can use that cache object. If the first session ends, then the next requestor of the cache will pick up responsibility for keeping the dataset up to date.
When I first implemented forms authentication I consulted an article that told me to store the user's custom IPrincipal object in the cache. Is this wrong? Should I have stored it in the session?
If I store all my user info, upon login, in cache and just have a "my account" page that displays the user info from cache, is that a good practice? I'm wondering if a person changes his email or does any type of database modification then the cached variables will be the wrong ones. If I have to update the cache variables every time something happens to the database, is this even a good practice compared to just querying the data whenever needed?
That out of the way, here's my situation: We are looking to port our existing classic ASP application to .NET, but we're unsure of what language to use for the new app.
I personally would 'prefer' C#, as I'm more familiar and comfortable with that languages way of doing things, but, the original code is VBScript, so it would possibly be easier to port to VB.NET ... One possible situation I fear would be that, because the code is so similar between the two variants of VB, that we might end up getting stuck on something that is not similar between the two, even though it looks like it would work. A shift to a wholly different language might avoid that kind of situation.
Does anyone have any practical examples of this kind of situation? Insights to illuminate the issue with? Do the potential benefits of a complete paradigm shift outweigh the gains from a high degree of 'copy-and-paste-ability' ?
We have a requirement from a client for porting an ASPX website to sharepoint :
Though the site is being served in ASPX there are no form submissions so effectively, they are just static pages without any server side processing required.
However, there is a common header and footer being used.
Here are some of the features being used in the existing site :
sifr for font substitution (using non standard web fonts) flash animations javascript and some jquery common header and footer for all pages
My question is how feasible is it to port this website to sharepoint ? Can i use sifr (or flash for that instance) in sharepoint ? or do i have to port it to silverlight ?
What is the general procedure for converting web applications to sharepoint ? Also i came across this [URL] for migration of website to sharepoint.
Can javascript be used in sharepoint ? How can i have common header and footer in sharepoint documents ?
My employer is changing hosting providers.Our current hosting provider offers MSSQL which we use for the database used on our website. The host we are changing to is insisting that we switch to MySQL because they only offer an older version of MSSQL and are concerned about compatibility issues.I have absolutely no experience working with MySQL and am a novice with MSSQL as well. What is the best way for me to port a database from one to the other?I have downloaded MySQL and Workbench... I've also downloaded the .Net connector as a zip file but am not sure where to extract its contents.
i am working in asp.net mvc & want to create a restful web service. how can i create a restful web service in MVC & how can i use it ? My requirement is : i have an application server which send some parameters to web service & the web service should connect to remote server & return image on path (whose path will be generated by the parameters from application server).
I simply want to create a fairly basic REST service, so that I can expose some of the data in my asp.net/SQL server application to the outside works, like this.....
http://domain.com/api/offices - would return an xml set of office locations. http://domain.com/api/offices/15 - would return all the details of office 15.
It's all fairly standard stuff (including basic authentication) but there seem to be several ways to achieve this using Microsoft technologies and I don't really know where to start. These seem to be the options...
1) WCF
2) ASP.NET MVC
3) ADO.NET Data Services
4) Rest Starter Kit project templates?
Which of these is the easiest and most "up-to-date" solution to creating a web service?
I have a restful controller that has your standard REST HTTP Verbs: Get,Post, Put, Delete. The problem I am having is that although my controllers are decorated to accept these verbs, when I execute my REST action, it can only hit my Get and Post methods. I have the attributes on top of the controller actions: HttPut, HttpDelete, HttpPost, and HttpGet. I also have the the override method in my forms: @Html.HttpMethodOverride(HttpVerbs.Put) When I submit my form, I get a 404 error from IIS 7.5, saying the static file handler couldn't find the resource. Strangely the same forms work in Cassini, so I think it is something in IIS7.5's setup.
What do I need to do to get IIS 7.5 to handle REST verbs like PUT and DELETE with Asp.Net MVC 3? I have already removed WebDAV and have looked through the handlers but the ones I am modifying seem to do nothing. My current setup is Asp.Net MVC 3, IIS7.5 on Windows 7.
I am using VS2008 pro to develop my web application. my project target framework is 3.5. I can add web service (.asmx) to it. But there is no .svc for me to add, do I need to install WCF REST Starter Kit? (but it is only in Preview 2)Or should I add an WCF service project to my solution?
i am in the process of creating a restful service with WCF, the service is likely to be consumed by at least 500 people at any given time. What settings would i need to set in order to deal with this.
I have created a server product that is connecting to some social network servers and sending to data which status update etc. The server already authenticated to necessary social networks servers by users who is using this solution.
Actually, I have no problem at this time, but I think I will.
My server will be open a thousands of concurrent request to neccessary servers via Http with C# HttpWebRequest instance. I already know that It's possible to change concurrent request limits with below propery.
ServicePointManager.DefaultConnectionLimit AFAIK, this limit is max 100 evet you set more than 100. So, I will be faced with bottleneck problem with HttpWebRequest even change the DefaultConnectionLimit property of ServicePointManager.
First, I'm looking for a a small example of how to handle a series of RESTful URLs, such as /Account/{userName} and /Account/{userName}/Profile with a single HttpHandler. At this time, I'm not interested in embracing MVC or using the REST Starter Kit. Should I place the HttpHandler class in a Class Library? Should I publish to the root of the RESTful URL?
My second issue stems from the fact that my ASP.NET hosting is done through a web-hosting company. Will I need to ask their tech team to configure IIS for me? Is that normal practice?
I want to implement a restful service in ASP.NET. I want it to be compatible with .Net 2.0 and IIS 5+. I am constrained to not use ASP.NET MVC or REST starter kit. By reading on internet I have learned that it can be implemented using HTTPHandlers. The problem is, the request will come in as a POST request. And I want to URL to be like:
http://abc.com/MyService/MyMethod1/ and http://abc.com/MyService/MyMethod2/
I have a File Uploader in my ASP.NET application Using C#, we can upload any type like images, documents, pdf etc.
I m storing it in the Filesystem and having only the Name of the File in DB.My doubt is can we store the entire file, images in DB. State me Which is good practice and why we need to use it.
We have a wfc layer that wraps the business classes and database access and use a client that lives on the database layer. Amongst our group we are attempting to form standards. Some want to have the client call the web method and pass the page they are requesting and the page size. Pass that to the database and then page in SQL Server use RowNum.Some want to cache the full list of objects in http cache on the service tier and page in memory. They concern here is memory use on the server.
Which would be best for a medium number of users with potentially large number of records to manage (say 30K) Is it better to cache them all in memory and work from there or page at the database as the application scales?
We have a data driven ASP.NET website which has been written using the standard pattern for data caching (adapted here from MSDN):
public DataTable GetData() { string key = "DataTable"; object item = Cache[key] as DataTable;
[code]...
The trouble with this is that the call to GetDataFromSQL() is expensive and the use of the site is fairly high. So every five minutes, when the cache drops, the site becomes very 'sticky' while a lot of requests are waiting for the new data to be retrieved.
What we really want to happen is for the old data to remain current while new data is periodically reloaded in the background. (The fact that someone might therefore see data that is six minutes old isn't a big issue - the data isn't that time sensitive). This is something that I can write myself, but it would be useful to know if any alternative caching engines (I know names like Velocity, memcache) support this kind of scenario. Or am I missing some obvious trick with the standard ASP.NET data cache?
we have so many parameters that the cache key is several hundred characters long. is there a limit to the length of these cache keys? Internally, it is using a dictionary, so theoretically the lookup time should be constant. However, I wonder if we have potential to run into some performance/memory problem.
I have use Nhibernate in my MVC Project by me known, Nhibernate have cache on Session and Object. now, I want use HttpContext.Current.Cache (system.web) for cache data something in project. my code same that have problem, haven't it. and that's right or wrong.
