Hi... I have tryed my best to understand the asp.net, but the visual of
asp.net pages are the most complicated, because on asp we have total control
over the layout the page, on the asp.net for example we have a lot of
components, like tables wich already have paging, etc.. a lot of code must
be rewritten...
I am having a lot of dificulties to try converting my asp projects to
asp.net... what do you think about this?
Paulo wrote:
> Hi... I have tryed my best to understand the asp.net, but the visual
> of asp.net pages are the most complicated, because on asp we have
> total control over the layout the page, on the asp.net for example we
> have a lot of components, like tables wich already have paging, etc..
> a lot of code must be rewritten...
>
> I am having a lot of dificulties to try converting my asp projects to
> asp.net... what do you think about this?
I'm not sure what to think about this, except ...
There was no way for you to know it (except maybe by browsing through some
of the previous questions in this newsgroup before posting yours - always a
recommended practice) , but this is a classic asp newsgroup. ASP.Net bears
very little resemblance to classic ASP so, while you may be lucky enough to
find a dotnet-knowledgeable person here who can answer your question, you
can eliminate the luck factor by posting your question to a group where
those dotnet-knowledgeable people hang out. I suggest
microsoft.public.dotnet.framework.aspnet.
If there is no need to convert, then don't convert.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
"Paulo"
news:%23YVEWjhQHHA.488@TK2MSFTNGP06.phx.gbl...
> Hi... I have tryed my best to understand the asp.net, but the visual of
> asp.net pages are the most complicated, because on asp we have total
> control over the layout the page, on the asp.net for example we have a lot
> of components, like tables wich already have paging, etc.. a lot of code
> must be rewritten...
>
> I am having a lot of dificulties to try converting my asp projects to
> asp.net... what do you think about this?
>
I have been using ASP.NET lately, it has some really good points about it.
but the controls are not one of them as far as I'm concerned.
The use of classes and web services and the ability to post info and return
info to the server without reloading the page are the points I like.
"Paulo"
news:%23YVEWjhQHHA.488@TK2MSFTNGP06.phx.gbl...
> Hi... I have tryed my best to understand the asp.net, but the visual of
> asp.net pages are the most complicated, because on asp we have total
> control over the layout the page, on the asp.net for example we have a lot
> of components, like tables wich already have paging, etc.. a lot of code
> must be rewritten...
>
> I am having a lot of dificulties to try converting my asp projects to
> asp.net... what do you think about this?
You have total control over the layout in ASP.Net. You just need to know
what you are doing. That means you must make the effort to learn it
properly, and that takes time. It's a lot more complicated than classic
ASP. If you are incapable of understanding it no matter how hard you try,
then ASP.Net is not for you.
And yes, since you a changing to a diffferent technology, your pages will
have to be re-written. ASP and ASP.Net have nothing in common.
--
Mike Brind
"Paulo"
news:%23YVEWjhQHHA.488@TK2MSFTNGP06.phx.gbl...
> Hi... I have tryed my best to understand the asp.net, but the visual of
> asp.net pages are the most complicated, because on asp we have total
control
> over the layout the page, on the asp.net for example we have a lot of
> components, like tables wich already have paging, etc.. a lot of code must
> be rewritten...
>
> I am having a lot of dificulties to try converting my asp projects to
> asp.net... what do you think about this?
>
Dig deeper and you may find that you can merge your existing 'controls' with
ASP.NET by building your own controls deriving from WebControl.
See:-
http://msdn2.microsoft.com/en-us/library/yhzc935f(vs.80).asp x
Hence you can leverage your existing client side JScript in your new Server
side ASP.NET controls.
As with all things greater flexibility equates to greater complexity.
ASP.NET is considerably more flexibile hence considerably more complex as a
product.
There is a lot more to learn (worse a zillion more different ways to skin
the same cat) and if your going to use it you do need to learn a great deal
if only to be sure you are using it to best effect and not re-inventing
something already present.