2 Questions ASP.NET

  • Thread starter Thread starter KJ
  • Start date Start date
K

KJ

First question, this should be easy. Where do you put the sql
connection string for a asp.net INTERNET app? The network people are
worried about putting the connection string in the web.config file on
the internet.

Second question, I know this has been talked about so much. But every
post I read does not outline the advantages vs. disadvantages of Grid
layout. My company is going to .NET from a VB 6 desktop environment
and we are trying to construct standards. Can someone list the
advantages and disadvantages of Grid layout. Everyone will be using IE
but might have diferent screen resolutions. Is this a problem?

Thanks for all responses.
 
If someone has access to your web.config, that means they already hacked
into your machine, so you are pretty much screwed already.
You could encrypt your information and store it in some file - and then
decrypt it in your app. But you would have to manually write something like
this.

Advantages:
Easier to use

Disadvantages:
Doesn't work well with objects that change in size or are visible based on
conditions. If you have a grid and a button underneath - if the grid ends up
with too many rows, it will cover the button.

I would guess it is virtually impossible to write a commercial application
using grid layout - no one would want to. Most people end up using another
product for the layout of the UI anyway, not vs.net.
 
Second Question:
<<Everyone will be using IE but might have diferent screen resolutions. Is
this a problem?>>
Yes - but more like a fact you have to recognize and account for in your
page design than a "problem" you have to solve.

Making the switch from VB6 forms to HTML for your page layouts is not going
to be easy if you have little or no HTML experience. Most non trivial page
layout work I am aware of is NOT done in Visual Studio... rather it's done
in Dreamweaver, FrontPage or some other specialized HTML/CSS Editor.
Personally, I'd rather use Notepad to manually edit HTML than use Visual
Studio for page layout work. So for most non trivial ASP.NET projects I've
participated in or heard of, it's Visual Studio for programming/code-behind
work, and another tool altogether for page layout and site management.

-GH
 
First question, this should be easy. Where do you put the sql
connection string for a asp.net INTERNET app? The network people are
worried about putting the connection string in the web.config file on
the internet.
Click to expand...

Ask your network people if they are concerned about any other files and
folders on the server machine. The web.config file is not browsable, so it
is as safe as the C:\Windows folder. Sounds like you might need to hire some
REAL network people.
Second question, I know this has been talked about so much. But every
post I read does not outline the advantages vs. disadvantages of Grid
layout. My company is going to .NET from a VB 6 desktop environment
and we are trying to construct standards. Can someone list the
advantages and disadvantages of Grid layout. Everyone will be using IE
but might have diferent screen resolutions. Is this a problem?
Click to expand...

In general, Grid Layout indicates that you are using CSS for layout; Flow
layout indicates that you are using HTML tables. However, it really doesn't
matter which you use; I use external CSS for layout, so I use Flow Layout
(but not tables), to prevent any inline styles from showing up in my HTML.
VS.Net uses inline CSS by default, which is possibly the worst of both
worlds. Using tables can make code maintenance difficult, but requires less
expertise than using CSS alone. Using CSS alone, with an external style
sheet, makes code maintenance a snap, and the entire layout can be changed
without touching any ASP.Net code, either in the Page Template, or in the
CodeBehind.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Neither a follower
nor a lender be.
 
Back
Top