3 new messages in 2 topics - digest

== 1 of 2 ==
Date: Fri, May 9 2008 7:46 pm
From: gnewsgroup


Mark Rae [MVP] wrote:
> "gnewsgroup" <gnewsgroup@gmail.com> wrote in message
> news:9393545e-f3e0-4be0-a5fa-bc83cf28a51b@t54g2000hsg.googlegroups.com...
>
> > Thank you. I also thought that they are simply letting the web server
> > retrieve the pre-defined default file.   But, then only one file per
> > folder will be retrieved. Isn't that too troublesome?
>
> Depends on your requirements, I suppose...
>
> > BTW, how do u tell it is not URL rewriting?
>
> Experience.
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

OK. thank you. In any case, I can get the same effect thru url
rewriting, right?




== 2 of 2 ==
Date: Fri, May 9 2008 7:54 pm
From: gnewsgroup


Michael Nemtsev [ MVP ] wrote:
> Hello gnewsgroup,
>
> if you look on their site stucture, u will see that they have the different
> url for each page, which could means that all pages are just index.aspx or
> default.aspx . Actually I checked into Fiddler and it's php pages.
>
> so, if u type /index.php in the end of url in will open you the same page,
> but not the index2.php
>
> ---
> WBR,
> Michael  Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour
>
> "The greatest danger for most of us is not that our aim is too high and we
> miss it, but that it is too low and we reach it" (c) Michelangelo
>
>
> g> Mark Rae [MVP] wrote:
> g>
> >> "gnewsgroup" <gnewsgroup@gmail.com> wrote in message
> >> news:35f2929e-927d-4477-9ffb-e214c1918683@24g2000hsh.googlegroups.com
> >> ...
> >>
> >>> I see you guys talking about URL rewriting, and then I came across
> >>> www.actioncarting.com, where no page seem to have an extension
> >>> like .aspx, .html, .shtml, .asp, .jsp, .php.  Is this trick
> >>> so-called
> >>> URL rewriting?
> >> No.
> >>
> >>> I would like to learn this little trick.
> >>>
> >> No trick. All they're doing is specifying a folder rather than a
> >> file. This
> >>
> >> way, ASP.NET / IIS will search for a "default" document and use one
> >> if it
> >>
> >> exists:
> >>
> >> http://www.google.co.uk/search?sourceid=navclient&hl=en-GB&ie=UTF-8&r
> >>
lz=1T4GZEZ_en-GBGB252GB252&q=IIS+default+document
> >>
> >> --
> >> Mark Rae
> >> ASP.NET MVP
> >> http://www.markrae.net
> g> Thank you. I also thought that they are simply letting the web server
> g> retrieve the pre-defined default file.   But, then only one file per
> g> folder will be retrieved. Isn't that too troublesome?
> g>
> g> BTW, how do u tell it is not URL rewriting?  Thanks again.
> g>

That's what I thought, but dismissed it bec'z I think it is too
troublesome to have to create one folder per file.





==============================================================================
TOPIC: How use NOW() function in InsertCommand
http://groups.google.com/group/microsoft.public.dotnet.framework.aspnet/browse_thread/thread/a20e1ca0bc72af19?hl=en
==============================================================================

== 1 of 1 ==
Date: Fri, May 9 2008 8:18 pm
From: "Mark Fitzpatrick"


Why not just use what the database has built into it. In this case just pass
the fucntion as one of your values. For example, in SQL Server it would be
GetDate() and used like so:

... @CompanyName, @CompanyLocation, GetDate(), 0)"

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression

"Cirene" <cirene@nowhere.com> wrote in message
news:u2adMKksIHA.2064@TK2MSFTNGP05.phx.gbl...
> In my HTML view of my ASPX page how do I use the NOW() function for the
> InsertCommand?   This doesn't seem to work...
>
> Code snippet:
>        <asp:SqlDataSource ID="sdsPress" runat="server"
>            ConnectionString="<%$ ConnectionStrings:ConnectionString %>"
>            DeleteCommand="DELETE FROM [pressReleases] WHERE [Id] = @Id"
>            InsertCommand="INSERT INTO [pressReleases] ([UserId],
> [PressTitle], [PressDescription], [CompanyName], [CompanyLocation],
> [DateAdded], [Flagged]) VALUES (@UserId, @PressTitle, @PressDescription,
> @CompanyName, @CompanyLocation, <% =Date.now() %>, 0)"
>
>
>





No comments: