Showing posts with label developing. Show all posts
Showing posts with label developing. Show all posts

Wednesday, March 28, 2012

Installation problems

I have been developing with AJAX since the release.
Now I received a new client computer and had to install all software again.
Everything went fine except AJAX where I received an odd error message.

1) I downloaded the file ASPAJAXExtSetup.msi
2) I tried to launch it but repeatedly get the following error:
"A network error occurred while attempting to read from the file ASPAJAXExtSetup.msi"

I tried to download it to all kinds of local folders but without any difference.
What kind of network error could that be?
IIS is installed and set to ASP 2.0.
Is there something obvious that I forgot this time?

i am having the exact same issue, did you ever get it working?


Yes, I asked the dotnet forum and finally got this advice:

The workaround is to use Windows Installer Cleanup Utility to remove the AJAX entry and then run setup again.

#Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301

Saturday, March 24, 2012

Is a WebService a Place to Put General Support Routines?

Let's assume that I am developing several different projects for different clients. Along the way, I may come up with "service routines" which can be generalized (such as recording some progresss or other info in a database table common to all of the different clients -- separately, of course).

If a WebService a good place to place these? Assuming that everything (database connection, etc.) can be passed in, would there be any reason why such a "service package" shouldn't be deployed in this way?

Hints, suggestions appreciated ... :) KevInKauai

Technically, you can, but unless you have a distributed system what does it gain you?

Why not write a common data layer component to use in all of your projects? This will give you the advantage of re-use without impact on performance.

Web services are very useful, but I doubt if they are necessary in your scenario.


Still not clear about the resusablity issue, Are planning to consume the WebService from all client ajax application?