I know that I'd still need a UI to connect to the web sevice and I would do
that in web forms.
What I'm strugging with is whether it makes sense to create a web service
(containing the methods that will perform the business logic) versus a web
forms application or web site. In my situation, I don't have a client or
interface requiring xml (I'm more concerned that an xml-based web service
would hurt performance). What I do have is a set of security requirments that
may be harder to implement in a web service (???). I guess that's my main
concern. I don't want to go down this path unless I can find a good reason
why a web service makes more sense.
Thanks for all the advice
Mardy
[quoted text, click to view] "Chad Z. Hower aka Kudzu" wrote:
> "=?Utf-8?B?TWFyZHk=?=" <Mardy@discussions.microsoft.com> wrote in
> news:DFC9E25D-F2B0-40FA-B138-F56C1DB2626F@microsoft.com:
> > I'm a long time asp developer but new to asp.net and web services. I
> > have been asked to develop an asp.net application and I'm not sure if I
> > should create it as a web forms app or a web service. Requirements are
> > as follows: -Must be able to use session variables or some other
> > approach to store user information and probably some datasets.
> > -Must implement a role based security model to restrict access to data.
> > -Application will be used on an Intranet but some users will browse in
> > from the internet through a firewall.
> > -SQL Server backend, integration with Microsoft Reporting Services for
> > reporting.
> > -Will serve as a template for identical applications deployed at other
> > clients.
>
> It really depends on what your UI will be. Webforms makes a web UI,
> WebServices does not.
>
>
> --
> Chad Z. Hower (a.k.a. Kudzu) -
http://www.hower.org/Kudzu/ > "Programming is an art form that fights back"
>
> Blog:
http://blogs.atozed.com/kudzu
On Sun, 29 May 2005 16:47:10 -0700, "Mardy"
[quoted text, click to view] <Mardy@discussions.microsoft.com> wrote:
>I'm a long time asp developer but new to asp.net and web services. I have
>been asked to develop an asp.net application and I'm not sure if I should
>create it as a web forms app or a web service. Requirements are as follows:
>-Must be able to use session variables or some other approach to store user
>information and probably some datasets.
>-Must implement a role based security model to restrict access to data.
>-Application will be used on an Intranet but some users will browse in from
>the internet through a firewall.
>-SQL Server backend, integration with Microsoft Reporting Services for
>reporting.
>-Will serve as a template for identical applications deployed at other
>clients.
>
The requirements are ... well let us not go there.
Create the "application" as a web service using the desired security
mechanism. Clients of this web service can be either desktop apps or
web form apps run in a browser.
You'll need a mule to test the web service so write a web forms
client. Next write a desktop client for the webservice. Ideally the
same business-logic classes can be used in both clients.
That pretty much covers all the bases. Everything else is just details
most of which lie within/behind the web service.
regards
A.G.
