I am writing a fake copy of a third party web service so that we can develop and test our application.
I need to emulate the functionality that allows the user to submit data, and then at some points the processing results on the service can be retrieved. What I need to do is to keep the submitted data in place, and receive it later (not in the same session). What I want to do is keep the database on the data (simple solution), but the environment that hosts the fake service does not allow it for it
I have the IsolatedStorage (application-scoped) Tried to use, but it does not seem to work in my example. (I'm using the following to get the store ...
isolated storage file.NetStore (Islaooted storage scope.app | separate storageScope. Assembly, blank, blank); I think that's my question (I keep in mind the fact that I understand the limitations of separate storage) How would I have to go about working it? If there is any consistent No way, so i guess I have to fall back on the file system to maintain a specific file location, and all the pain in the permission setting in our environment.
self-action.
For Dev and testing projects, I realized that the lifespan of permanent objects will be the easiest to limit and
to store HttpRuntime items. Cache Enough flexibility to Tne.
Comments
Post a Comment