tables & rows & columns

I have a table that doesn't line up the way I want it to. I have 6 rows and
3 columns. The 3rd column spans the 6 rows and contains a grid. If the
data in the grid has more than 6 rows of data, the other rows spread out
vertically, as if there is extra space in there. I don't want that to
happen, I want the 6 rows to be together as if there is no space between
then. I have tried using height, valign, using a set height and using a
percentage height and it doesn't work. How can I make the 6 rows on the
left align all the way to the top?
<table borderColor=red cellSpacing=0 cellPadding=0 width="100%" border=1
runat="server" ID="Table1">
<tr vAlign=top colspan=4><td> </td></tr>
<tr vAlign=top>
<td valign=top style="HEIGHT: 15px" align=left width=100>Col 1</td>
<td vAlign=top height=5>Col 2</td>
<td align=right rowspan=6>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col
3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col
3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br></td>
<td align=left rowspan=6>Col 4</td></tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
</table>Maybe I didn't really get your question, but I do not see a grid in the
3rd column.
But did you try to put another table into one cell? That often works.
Remy Blaettler
www.collaboral.com

tables & rows & columns

I have a table that doesn't line up the way I want it to. I have 6 rows and
3 columns. The 3rd column spans the 6 rows and contains a grid. If the
data in the grid has more than 6 rows of data, the other rows spread out
vertically, as if there is extra space in there. I don't want that to
happen, I want the 6 rows to be together as if there is no space between
then. I have tried using height, valign, using a set height and using a
percentage height and it doesn't work. How can I make the 6 rows on the
left align all the way to the top?

<table borderColor=red cellSpacing=0 cellPadding=0 width="100%" border=1
runat="server" ID="Table1">
<tr vAlign=top colspan=4><td> </td></tr
<tr vAlign=top>
<td valign=top style="HEIGHT: 15px" align=left width=100>Col 1</td>
<td vAlign=top height=5>Col 2</td>
<td align=right rowspan=6>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col
3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col
3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br>Col 3<br></td>
<td align=left rowspan=6>Col 4</td></tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top height=1>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr>
<tr valign=top>
<td valign=top>col 1</td>
<td valign=top>col 2</td>
</tr
</tableMaybe I didn't really get your question, but I do not see a grid in the
3rd column.
But did you try to put another table into one cell? That often works.

Remy Blaettler
www.collaboral.com

tabpanels have a white strip on them

Hi! I am using a Ajax tabcontainer, but the buttons are not displayed properly, there us like a while line about 4pxheight that crosses all the buttons. Here is the code I am using:

<asp:ContentID="Content1"ContentPlaceHolderID="BodyContent"Runat="Server">

<asp:ScriptManagerID="ScriptManager1"runat="server">

</asp:ScriptManager>

<cc1:TabContainerID="TabContainer1"runat="server"ActiveTabIndex="2"Height="369px">

<cc1:TabPanelID="TabPanel1"runat="server"HeaderText="TabPanel1">

<HeaderTemplate>

TabPanel1

</HeaderTemplate>

</cc1:TabPanel>

<cc1:TabPanelID="TabPanel2"runat="server"HeaderText="TabPanel2">

<HeaderTemplate>

TabPanel2<br/>

</HeaderTemplate>

</cc1:TabPanel>

<cc1:TabPanelID="TabPanel3"runat="server"HeaderText="TabPanel3">

</cc1:TabPanel>

</cc1:TabContainer>

</asp:Content>

Do I have to configure something else?? Thanks!

I did the same thing in a regular page and it worked fine. Why is the master page messing it up? Thanks!

I figured where the problem is from, I am using:<htmlxmlns="http://www.w3.org/1999/xhtml"> instead of

<!DOCTYPEhtmlPUBLIC"-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

But now all pages are messed up when I put <!DOCTYPEhtmlPUBLIC"-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> like the footer gets bigger...

tabs and line breaks lost in Outlook Express

Hi, Folks --

Not sure this is the right forum for this, but I thought I'd try.

I'm sending out emails from my ASP.NET app using the SmtpClient and MailMessage classes. Easy as pie to do this, but the problem is that the \t and \r characters that I include in the MailMessage body are ignored in Outlook Express, so I end up with a big blob of text.

This problem does not occur in Lotus Notes or when I view the emails on the Web.

Any suggestions are greatly appreciated.

Thanks,

Eric

I know outlook express automatically removes extra line breaks from messages. I'm not sure if thats what your encountering.

I'm assuming because your using \t and \r that you arent doing an html body message...is that a possibility or no?

You can try instead of using the \t and \r to use the Chr(13) and chr(20) ASCII designation for whatever language your using, unfortunatly if your using a string literal you may end up with that printed in your message.

Thanks, F.

Using \n instead of \r solved the line break problem in Outlook Express. (I still have to check this in Lotus Notes, but I don't anticipate a problem.)

I also ended up specifying:

message.BodyEncoding = System.Text.

Encoding.UTF8;

for good measure, even though this wasn't necessary for the line break issue.

As for the tabs, could not get them to work, but I'm going to avoid these anyway because the number of spaces rendered per tab is a pain to try to adjust.

Eric

Take Application off line quickly

Suppose I need to make an ASP.NET Web application inaccessible to anyone
trying to open any of its pages. How can this be done quickly - and in a way
that allows me to bring the whole thing back online quickly?1) Shut down IIS - of course this will give them a page not found type of
error
2) You can configure a virtual directory in IIS to redirect to a given URL.
This URL can then inform the user that the site is down and to try again
later. This would probably be more user friendly.
"Guadala Harry" <GMan@.NoSpam.com> wrote in message
news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Suppose I need to make an ASP.NET Web application inaccessible to anyone
> trying to open any of its pages. How can this be done quickly - and in a
way
> that allows me to bring the whole thing back online quickly?
>
You could just stop the IIS site. You could also hanlde this in the app
itself if needed (especially if it could be interesting to "filter" those
who are allowed to log on when the app is in this particular state).
The overall goal may yield a better suggestion.
Patrice
"Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Suppose I need to make an ASP.NET Web application inaccessible to anyone
> trying to open any of its pages. How can this be done quickly - and in a
way
> that allows me to bring the whole thing back online quickly?
>
Yes - the overall goal (small detail!): Here it is: I have to periodically
bring a site down for maintenance (anywhere from 2 minutes to 2 hours;
install upgaded assemblies, updated aspx files, modify database etc); during
which period I don't want anyone to come in - and after which I want to
allow everyone back in of course. I don't mind killing existing sessions
(could easily pick a time of day to minimize such occurances in this
low-volume application). It would be great if the user could see some
informative message when they attempt to open any page in the site - rather
than some error that drives them to call tech support.
Thanks!
-GH
"Patrice" <nobody@.nowhere.com> wrote in message
news:uAZQII8rEHA.4008@.TK2MSFTNGP14.phx.gbl...
> You could just stop the IIS site. You could also hanlde this in the app
> itself if needed (especially if it could be interesting to "filter" those
> who are allowed to log on when the app is in this particular state).
> The overall goal may yield a better suggestion.
> Patrice
> --
> "Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
> news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> way
>
Ok so you have the options :
- virtual dir as suggested by Marina
- adding this into the app will allow some accounts to connect so that you
can check that it works before bringing things online again.
As a side note, I believe to have read that ASP.NET actually caches the DLLs
(including ASPX code behind) so that you can update DLLs and pages "on the
fly". You could ask this in a separate thread. For the database, you could
prepare a script.
Though I admit we have no high volume (vertical applications) and that users
are generally located in the same country (allowing to update during lunch
or after the day work), IMO you could look also if you can shorten the time
it takes to perform this update and in some cases it could be even almost
useless to "close" the site.
As an additonal note, you may want also to display a "message of the day"
*before* the update so that they know the site *will* be updated while they
work. Bascially I would see :
- Schelded date for the next update and expected duratino (few days before)
- a warning message or blocking the site during the update (tyhat should be
IMO almost "automated" ie blocking or anbeling the warning, copying prepared
files to update DLLs and pages, running a script)
- you do the final check by hand and can correct what unexpectedly goes
wrong
- when all is ok, you manually enable the site again
Patrice
"Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
news:ObCupT8rEHA.736@.tk2msftngp13.phx.gbl...
> Yes - the overall goal (small detail!): Here it is: I have to
periodically
> bring a site down for maintenance (anywhere from 2 minutes to 2 hours;
> install upgaded assemblies, updated aspx files, modify database etc);
during
> which period I don't want anyone to come in - and after which I want to
> allow everyone back in of course. I don't mind killing existing sessions
> (could easily pick a time of day to minimize such occurances in this
> low-volume application). It would be great if the user could see some
> informative message when they attempt to open any page in the site -
rather
> than some error that drives them to call tech support.
> Thanks!
> -GH
>
> "Patrice" <nobody@.nowhere.com> wrote in message
> news:uAZQII8rEHA.4008@.TK2MSFTNGP14.phx.gbl...
those
anyone
a
>
Thanks!
"Patrice" <nobody@.nowhere.com> wrote in message
news:eLAomg8rEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Ok so you have the options :
> - virtual dir as suggested by Marina
> - adding this into the app will allow some accounts to connect so that you
> can check that it works before bringing things online again.
> As a side note, I believe to have read that ASP.NET actually caches the
DLLs
> (including ASPX code behind) so that you can update DLLs and pages "on the
> fly". You could ask this in a separate thread. For the database, you could
> prepare a script.
> Though I admit we have no high volume (vertical applications) and that
users
> are generally located in the same country (allowing to update during lunch
> or after the day work), IMO you could look also if you can shorten the
time
> it takes to perform this update and in some cases it could be even almost
> useless to "close" the site.
> As an additonal note, you may want also to display a "message of the day"
> *before* the update so that they know the site *will* be updated while
they
> work. Bascially I would see :
> - Schelded date for the next update and expected duratino (few days
before)
> - a warning message or blocking the site during the update (tyhat should
be
> IMO almost "automated" ie blocking or anbeling the warning, copying
prepared
> files to update DLLs and pages, running a script)
> - you do the final check by hand and can correct what unexpectedly goes
> wrong
> - when all is ok, you manually enable the site again
> Patrice
> --
> "Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
> news:ObCupT8rEHA.736@.tk2msftngp13.phx.gbl...
> periodically
> during
> rather
app
> those
> anyone
in
> a
>

Take Application off line quickly

Suppose I need to make an ASP.NET Web application inaccessible to anyone
trying to open any of its pages. How can this be done quickly - and in a way
that allows me to bring the whole thing back online quickly?1) Shut down IIS - of course this will give them a page not found type of
error
2) You can configure a virtual directory in IIS to redirect to a given URL.
This URL can then inform the user that the site is down and to try again
later. This would probably be more user friendly.

"Guadala Harry" <GMan@.NoSpam.com> wrote in message
news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Suppose I need to make an ASP.NET Web application inaccessible to anyone
> trying to open any of its pages. How can this be done quickly - and in a
way
> that allows me to bring the whole thing back online quickly?
You could just stop the IIS site. You could also hanlde this in the app
itself if needed (especially if it could be interesting to "filter" those
who are allowed to log on when the app is in this particular state).

The overall goal may yield a better suggestion.

Patrice

--

"Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Suppose I need to make an ASP.NET Web application inaccessible to anyone
> trying to open any of its pages. How can this be done quickly - and in a
way
> that allows me to bring the whole thing back online quickly?
Yes - the overall goal (small detail!): Here it is: I have to periodically
bring a site down for maintenance (anywhere from 2 minutes to 2 hours;
install upgaded assemblies, updated aspx files, modify database etc); during
which period I don't want anyone to come in - and after which I want to
allow everyone back in of course. I don't mind killing existing sessions
(could easily pick a time of day to minimize such occurances in this
low-volume application). It would be great if the user could see some
informative message when they attempt to open any page in the site - rather
than some error that drives them to call tech support.

Thanks!

-GH

"Patrice" <nobody@.nowhere.com> wrote in message
news:uAZQII8rEHA.4008@.TK2MSFTNGP14.phx.gbl...
> You could just stop the IIS site. You could also hanlde this in the app
> itself if needed (especially if it could be interesting to "filter" those
> who are allowed to log on when the app is in this particular state).
> The overall goal may yield a better suggestion.
> Patrice
> --
> "Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
> news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> > Suppose I need to make an ASP.NET Web application inaccessible to anyone
> > trying to open any of its pages. How can this be done quickly - and in a
> way
> > that allows me to bring the whole thing back online quickly?
Ok so you have the options :
- virtual dir as suggested by Marina
- adding this into the app will allow some accounts to connect so that you
can check that it works before bringing things online again.

As a side note, I believe to have read that ASP.NET actually caches the DLLs
(including ASPX code behind) so that you can update DLLs and pages "on the
fly". You could ask this in a separate thread. For the database, you could
prepare a script.

Though I admit we have no high volume (vertical applications) and that users
are generally located in the same country (allowing to update during lunch
or after the day work), IMO you could look also if you can shorten the time
it takes to perform this update and in some cases it could be even almost
useless to "close" the site.

As an additonal note, you may want also to display a "message of the day"
*before* the update so that they know the site *will* be updated while they
work. Bascially I would see :
- Schelded date for the next update and expected duratino (few days before)
- a warning message or blocking the site during the update (tyhat should be
IMO almost "automated" ie blocking or anbeling the warning, copying prepared
files to update DLLs and pages, running a script)
- you do the final check by hand and can correct what unexpectedly goes
wrong
- when all is ok, you manually enable the site again

Patrice

--

"Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
news:ObCupT8rEHA.736@.tk2msftngp13.phx.gbl...
> Yes - the overall goal (small detail!): Here it is: I have to
periodically
> bring a site down for maintenance (anywhere from 2 minutes to 2 hours;
> install upgaded assemblies, updated aspx files, modify database etc);
during
> which period I don't want anyone to come in - and after which I want to
> allow everyone back in of course. I don't mind killing existing sessions
> (could easily pick a time of day to minimize such occurances in this
> low-volume application). It would be great if the user could see some
> informative message when they attempt to open any page in the site -
rather
> than some error that drives them to call tech support.
> Thanks!
> -GH
>
> "Patrice" <nobody@.nowhere.com> wrote in message
> news:uAZQII8rEHA.4008@.TK2MSFTNGP14.phx.gbl...
> > You could just stop the IIS site. You could also hanlde this in the app
> > itself if needed (especially if it could be interesting to "filter"
those
> > who are allowed to log on when the app is in this particular state).
> > The overall goal may yield a better suggestion.
> > Patrice
> > --
> > "Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
> > news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> > > Suppose I need to make an ASP.NET Web application inaccessible to
anyone
> > > trying to open any of its pages. How can this be done quickly - and in
a
> > way
> > > that allows me to bring the whole thing back online quickly?
> >
Thanks!

"Patrice" <nobody@.nowhere.com> wrote in message
news:eLAomg8rEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Ok so you have the options :
> - virtual dir as suggested by Marina
> - adding this into the app will allow some accounts to connect so that you
> can check that it works before bringing things online again.
> As a side note, I believe to have read that ASP.NET actually caches the
DLLs
> (including ASPX code behind) so that you can update DLLs and pages "on the
> fly". You could ask this in a separate thread. For the database, you could
> prepare a script.
> Though I admit we have no high volume (vertical applications) and that
users
> are generally located in the same country (allowing to update during lunch
> or after the day work), IMO you could look also if you can shorten the
time
> it takes to perform this update and in some cases it could be even almost
> useless to "close" the site.
> As an additonal note, you may want also to display a "message of the day"
> *before* the update so that they know the site *will* be updated while
they
> work. Bascially I would see :
> - Schelded date for the next update and expected duratino (few days
before)
> - a warning message or blocking the site during the update (tyhat should
be
> IMO almost "automated" ie blocking or anbeling the warning, copying
prepared
> files to update DLLs and pages, running a script)
> - you do the final check by hand and can correct what unexpectedly goes
> wrong
> - when all is ok, you manually enable the site again
> Patrice
> --
> "Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
> news:ObCupT8rEHA.736@.tk2msftngp13.phx.gbl...
> > Yes - the overall goal (small detail!): Here it is: I have to
> periodically
> > bring a site down for maintenance (anywhere from 2 minutes to 2 hours;
> > install upgaded assemblies, updated aspx files, modify database etc);
> during
> > which period I don't want anyone to come in - and after which I want to
> > allow everyone back in of course. I don't mind killing existing sessions
> > (could easily pick a time of day to minimize such occurances in this
> > low-volume application). It would be great if the user could see some
> > informative message when they attempt to open any page in the site -
> rather
> > than some error that drives them to call tech support.
> > Thanks!
> > -GH
> > "Patrice" <nobody@.nowhere.com> wrote in message
> > news:uAZQII8rEHA.4008@.TK2MSFTNGP14.phx.gbl...
> > > You could just stop the IIS site. You could also hanlde this in the
app
> > > itself if needed (especially if it could be interesting to "filter"
> those
> > > who are allowed to log on when the app is in this particular state).
> > > > The overall goal may yield a better suggestion.
> > > > Patrice
> > > > --
> > > > "Guadala Harry" <GMan@.NoSpam.com> a crit dans le message de
> > > news:uLeqQ17rEHA.1816@.TK2MSFTNGP09.phx.gbl...
> > > > Suppose I need to make an ASP.NET Web application inaccessible to
> anyone
> > > > trying to open any of its pages. How can this be done quickly - and
in
> a
> > > way
> > > > that allows me to bring the whole thing back online quickly?
> > > > > >