Thanks for the response Nicholas,
My specific issue is that I'm receiving error messages stating that I have
not assigned sufficient permissions to perform the operations. Reading
through the complexities of CAS, I am over my head trying to get my code
to
the users fast. This is due this month and I've got 3 days left before I'm
out "in training" for a week.
The application is a WinForm quick and dirty slide show requiring
FullPath,
FileIO, SQL access. I've created the ActiveDirectory groups in SQL Server
2K
and everything works using this role-based Windows security as far as old
school though goes. I'm catching a lot of heat because I can't just
code-n-go
like they are. It will eventually be an ASP.NET application used as a new
generator/posting application for these kiosks. I believe if you can
access
one path or one database in a domain, you can get to others, so the code
needs to be more secure than normal.
I do think more C-like than VB and picked up C# quickly. Now I just need
to
wrestle the requirements like CAS into submission (mentally).
Thanks for the response >>though I won't say anything regarding the
toy-like
nature of VB.NET. ;-]
E.
Nicholas Paldino said:
Esteban,
What is the issue that you are having? Not to start a language war
either, but in general, VB is not targeted towards the audience that is
concerned with such things. Right now, MS is marketing VB to the
hobbyist
programmer, and in general, programmers on that level are not going to be
concerned with things like CAS.
What specifically is your issue?
--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)
Not to start a lang war, but I asked a couple VB.NET people how they
resolved
a CAS issue I had using SQL adapters, FileIO operations and the like. I
got
some (quite a few) blank looks. Do VB.NET authors not have this issue
or
is
it possible their code is so benign it never used any secured
resources?
Most
of it is reading/writing to SQL tables. We're using the 1.1 framework
and
SDK.
Reading their code I saw and Import statements like these using
statements:
using System.Security.Permissions;
using System.Security;
What gives?
TIA,
E.