You'll want to add a reference to the COM component. This should create
a .NET Interop Assembly and put it in your bin folder. Once this is
complete, you should be set to go.

-----Original Message-----
From: Avnish Soni [mailto:Avnish.Soni@p...] 
Sent: Friday, August 09, 2002 08:30
To: ASPX_Professional
Subject: [aspx_professional] How to use existing COM in dot net app

Hello,

In my .net application i need to use my exisiting COM objects. What are
the
steps for that?

thanks
avi

-----Original Message-----
From: Nick Charlesworth [mailto:nick@f...]
Sent: Friday, August 09, 2002 11:50 AM
To: ASPX_Professional
Subject: [aspx_professional] RE: using different authentication modes in
the same application


Why do you think forms authentication is 'Limiting'.

Do you think it better to use a session variable to hold the userID
after 
a successful login and then check for this variable at the top of each 
page?

> That is the correct way to approach it, if you are limiting yourself
to
forms authentication. In some of my web apps, I plan on this when I do a
site map and information architecture by encoding the access level in
the page number. P for public pages, and they go in a sub folder called
public. M for member, and A for admin. I also usually have a global
resources folder with sub folders for images broken out by use, but each
P/M/A folder will also have its own local resource folder.

Brian Prince

-----Original Message-----
From: Nick Charlesworth [mailto:nick@f...]
Sent: Friday, August 09, 2002 10:13 AM
To: ASPX_Professional
Subject: [aspx_professional] using different authentication modes in the
same application


Hi,

Is it possible to use different authentication modes in the same
application.

i.e. A site that contains a shopping cart might want it's initial
home
page and contact us page to require no authentication but it's
shopping
cart checkout pages might require forms authentication.

If I enable forms authentication this means that all aspx files will
require a forms login before they can be accessed.

I do not want to make the home page .htm or .html as it must carry
out
other asp.net functionality.

Is the correct solution to allow anonymous access in the root
directory
and then place all pages requiring authentication in a sub folder
with
it's own web.config file that requires forms authentication?

If this works will application and session variables be carried
through
from non-authenticated pages to authenticated pages and vice-versa?

thanks,

Nick
---

ASP.NET 1.0 Namespace Reference with C#
http://www.wrox.com/acon11.asp?ISBN=3D1861007442

ASP.NET 1.0 Namespace Reference with VB.NET
http://www.wrox.com/acon11.asp?ISBN=3D1861007450

These books are a complete reference to the ASP.NET namespaces
for developers who are already familiar with using ASP.NET.
There is no trivial introductory material or useless .NET
hype and the presentation of the namespaces, in an easy-to use
alphabetical order ensures a user-friendly reference format.
We provide in-depth coverage of all the major ASP.NET classes,
giving you those real-world tips that the documentation doesn't
offer, and demonstrating complex techniques with simple
examples. 

---


<FONT face=3DArial size=3D1>
************************************************************************
***

****************************************
This message (including any attachments) contains confidential
information 

intended for a specific
individual and purpose, and is protected by law.  If you are not the 
intend
ed recipient, you should
delete this message.  Any disclosure, copying, or distribution of this 
mess
age, or the taking of any
action based on it, is strictly prohibited.

************************************************************************
***

****************************************
</FONT>

---

ASP.NET 1.0 Namespace Reference with C#
http://www.wrox.com/acon11.asp?ISBN=1861007442

ASP.NET 1.0 Namespace Reference with VB.NET
http://www.wrox.com/acon11.asp?ISBN=1861007450

These books are a complete reference to the ASP.NET namespaces 
for developers who are already familiar with using ASP.NET. 
There is no trivial introductory material or useless .NET 
hype and the presentation of the namespaces, in an easy-to use 
alphabetical order ensures a user-friendly reference format.
We provide in-depth coverage of all the major ASP.NET classes, 
giving you those real-world tips that the documentation doesn't 
offer, and demonstrating complex techniques with simple 
examples.  

---

http://www.patni.com  
World-Wide Partnerships. World-Class Solutions. 
-__________________________________________________________________   
  
The information transmitted is intended only for the person or entity to

which it is addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other use of, or 
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is prohibited.If
you 
received this in error, please contact the sender and delete the
material 
from any computer. 
-__________________________________________________________________

---

ASP.NET 1.0 Namespace Reference with C#
http://www.wrox.com/acon11.asp?ISBN=1861007442

ASP.NET 1.0 Namespace Reference with VB.NET
http://www.wrox.com/acon11.asp?ISBN=1861007450

These books are a complete reference to the ASP.NET namespaces 
for developers who are already familiar with using ASP.NET. 
There is no trivial introductory material or useless .NET 
hype and the presentation of the namespaces, in an easy-to use 
alphabetical order ensures a user-friendly reference format.
We provide in-depth coverage of all the major ASP.NET classes, 
giving you those real-world tips that the documentation doesn't 
offer, and demonstrating complex techniques with simple 
examples.  

---