Hi,
If I want to check permission on each public method of a web service,
(assume the checking routine is ready to use and called AccessCheck) , one
way of doing it is to call this AccessCheck on top of each public method, I
want to implement it in different way but seems missing something -
I want to develop a custom attribute, let's say
SecurityCheckEnabledAttribute with only Yes/No parameter, then create a base
class for all web service classes, Is there any way to capture the public
method call from base class at runtime and then check if the attribute is
being applied and then check the permission?
Thanks a lot!
Regards,
John 8 3156
Yes, but it's probably not as simple as you might have hoped. Here are the
three main approaches:
1. Implement the check as a custom permission with a corresponding
attribute
( http://msdn.microsoft.com/library/en...rmissions.asp).
This may be your best bet since you can presumably control whether the
attribute assembly is registered as a trusted assembly.
2. Place the actual method work in objects that inherit from
System.ContextBoundObject. This might interfere with your planned object
hierarchy, as well as introducing an otherwise unnecessary performance hit.
3. Use a tool like XC# ( http://www.resolvecorp.com/Products.aspx) to
generate inline code that corresponds to your custom attribute.
If this truly is a security permission, #1 is probably the "cleanest"
approach. Otherwise, #3 would probably offer the best compromise between
design-time convenience and runtime performance.
HTH,
Nicole
"John Lee" <jo***@newsgroup.nospam> wrote in message
news:ej****************@TK2MSFTNGP10.phx.gbl... Hi,
If I want to check permission on each public method of a web service, (assume the checking routine is ready to use and called AccessCheck) , one way of doing it is to call this AccessCheck on top of each public method, I want to implement it in different way but seems missing something -
I want to develop a custom attribute, let's say SecurityCheckEnabledAttribute with only Yes/No parameter, then create a base class for all web service classes, Is there any way to capture the public method call from base class at runtime and then check if the attribute is being applied and then check the permission?
Thanks a lot!
Regards, John
Hello!
Don't forget that if the Principal and/or Identity instances are expensive
to create, you might want to implement a caching schema to save resources.
--
venlig hilsen / with regards
anders borum (mcp)
--
Thanks very much for the reply.
But all role-based security information resides in AzMan store. All web
services are configured as Windows authentication in IIS. So I will have to
first get the Windows principal and then call AzRoles.dll's
AccessCheck("method name") - each method name will be defined as an
"operation" in AzMan store.
Regards,
John
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:Or****************@tk2msftngp13.phx.gbl... Or (and I think this is the easiest one of all), just use a custom principal, and let Code Access Security take care of the rest. Basically, you implement IPrincipal, and set it as the principal for the thread that is doing the processing.
Attached is a console application which demonstrates how to use the PrincipalPermission attribute. Basically, there is an implementation of IPrincipal and the current thread is set to use that principal (you will have to do something different to have web requests use a certain principal, but Im sure you can do it). Then, you just apply the right attribute to your method, and the runtime will take care of the rest.
Try changing the IsInRole implementation to return something else, or the declaration of the PrincipalPermission attribute and the call to DoSomething will fail.
Hope this helps.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:O5**************@TK2MSFTNGP12.phx.gbl... Yes, but it's probably not as simple as you might have hoped. Here are the three main approaches:
1. Implement the check as a custom permission with a corresponding attribute (http://msdn.microsoft.com/library/en...rmissions.asp). This may be your best bet since you can presumably control whether the attribute assembly is registered as a trusted assembly.
2. Place the actual method work in objects that inherit from System.ContextBoundObject. This might interfere with your planned object hierarchy, as well as introducing an otherwise unnecessary performance hit.
3. Use a tool like XC# (http://www.resolvecorp.com/Products.aspx) to generate inline code that corresponds to your custom attribute.
If this truly is a security permission, #1 is probably the "cleanest" approach. Otherwise, #3 would probably offer the best compromise between design-time convenience and runtime performance.
HTH, Nicole "John Lee" <jo***@newsgroup.nospam> wrote in message news:ej****************@TK2MSFTNGP10.phx.gbl... Hi,
If I want to check permission on each public method of a web service, (assume the checking routine is ready to use and called AccessCheck) , one way of doing it is to call this AccessCheck on top of each public method, I want to implement it in different way but seems missing something -
I want to develop a custom attribute, let's say SecurityCheckEnabledAttribute with only Yes/No parameter, then create a base class for all web service classes, Is there any way to capture the public method call from base class at runtime and then check if the attribute is being applied and then check the permission?
Thanks a lot!
Regards, John
Not sure why, but I didn't even consider that this might have anything to do
with the principal when I answered yesterday. That said, even if it is
reasonably simple to swap out the principal for a web service, it's still
not necessarily a great idea to do so. While using Windows-integrated
authentication for web services is certainly simple, investing additional
effort into tweaking the behaviour of a non-standard authentication
mechanism probably isn't the best use of most folks' time...
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:Or****************@tk2msftngp13.phx.gbl... Or (and I think this is the easiest one of all), just use a custom principal, and let Code Access Security take care of the rest. Basically, you implement IPrincipal, and set it as the principal for the thread that is doing the processing.
Attached is a console application which demonstrates how to use the PrincipalPermission attribute. Basically, there is an implementation of IPrincipal and the current thread is set to use that principal (you will have to do something different to have web requests use a certain principal, but Im sure you can do it). Then, you just apply the right attribute to your method, and the runtime will take care of the rest.
Try changing the IsInRole implementation to return something else, or the declaration of the PrincipalPermission attribute and the call to DoSomething will fail.
Hope this helps.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:O5**************@TK2MSFTNGP12.phx.gbl... Yes, but it's probably not as simple as you might have hoped. Here are the three main approaches:
1. Implement the check as a custom permission with a corresponding attribute (http://msdn.microsoft.com/library/en...rmissions.asp). This may be your best bet since you can presumably control whether the attribute assembly is registered as a trusted assembly.
2. Place the actual method work in objects that inherit from System.ContextBoundObject. This might interfere with your planned object hierarchy, as well as introducing an otherwise unnecessary performance hit.
3. Use a tool like XC# (http://www.resolvecorp.com/Products.aspx) to generate inline code that corresponds to your custom attribute.
If this truly is a security permission, #1 is probably the "cleanest" approach. Otherwise, #3 would probably offer the best compromise between design-time convenience and runtime performance.
HTH, Nicole "John Lee" <jo***@newsgroup.nospam> wrote in message news:ej****************@TK2MSFTNGP10.phx.gbl... Hi,
If I want to check permission on each public method of a web service, (assume the checking routine is ready to use and called AccessCheck) , one way of doing it is to call this AccessCheck on top of each public method, I want to implement it in different way but seems missing something -
I want to develop a custom attribute, let's say SecurityCheckEnabledAttribute with only Yes/No parameter, then create a base class for all web service classes, Is there any way to capture the public method call from base class at runtime and then check if the attribute is being applied and then check the permission?
Thanks a lot!
Regards, John
John,
Your biggest problem with this is likely to be determining the name of the
method. Unfortunately, the permissions attributes have no built-in
mechanism for directly retrieving a reference to the attribute target.
While it might be possible to retrieve such a reference using a combination
of stack walking and reflection at runtime, this would have potentially
undesirable performance consequences. To avoid these, you would need to
either hard-code the operation name (or some mapping value) into the
attribute definition (regardless of you're implementing with a custom
permission or a principal permission with custom principal) or use a tool
like XC# that will do the heavy lifting at compile time rather than at
runtime. Personally, I wouldn't opt for the hard-coding approach since
security holes could be opened by simply missing an edit during code
maintenance, but YMMV...
HTH,
Nicole
"John Lee" <jo***@newsgroup.nospam> wrote in message
news:uc*************@TK2MSFTNGP10.phx.gbl... Thanks very much for the reply.
But all role-based security information resides in AzMan store. All web services are configured as Windows authentication in IIS. So I will have to first get the Windows principal and then call AzRoles.dll's AccessCheck("method name") - each method name will be defined as an "operation" in AzMan store.
Regards, John
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:Or****************@tk2msftngp13.phx.gbl... Or (and I think this is the easiest one of all), just use a custom principal, and let Code Access Security take care of the rest. Basically, you implement IPrincipal, and set it as the principal for the thread that is doing the processing.
Attached is a console application which demonstrates how to use the PrincipalPermission attribute. Basically, there is an implementation of IPrincipal and the current thread is set to use that principal (you will have to do something different to have web requests use a certain principal, but Im sure you can do it). Then, you just apply the right attribute to your method, and the runtime will take care of the rest.
Try changing the IsInRole implementation to return something else, or the declaration of the PrincipalPermission attribute and the call to DoSomething will fail.
Hope this helps.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:O5**************@TK2MSFTNGP12.phx.gbl... Yes, but it's probably not as simple as you might have hoped. Here are the three main approaches:
1. Implement the check as a custom permission with a corresponding attribute (http://msdn.microsoft.com/library/en...rmissions.asp). This may be your best bet since you can presumably control whether the attribute assembly is registered as a trusted assembly.
2. Place the actual method work in objects that inherit from System.ContextBoundObject. This might interfere with your planned object hierarchy, as well as introducing an otherwise unnecessary performance hit.
3. Use a tool like XC# (http://www.resolvecorp.com/Products.aspx) to generate inline code that corresponds to your custom attribute.
If this truly is a security permission, #1 is probably the "cleanest" approach. Otherwise, #3 would probably offer the best compromise between design-time convenience and runtime performance.
HTH, Nicole "John Lee" <jo***@newsgroup.nospam> wrote in message news:ej****************@TK2MSFTNGP10.phx.gbl... Hi,
If I want to check permission on each public method of a web service, (assume the checking routine is ready to use and called AccessCheck) , one way of doing it is to call this AccessCheck on top of each public method, I want to implement it in different way but seems missing something -
I want to develop a custom attribute, let's say SecurityCheckEnabledAttribute with only Yes/No parameter, then create a base class for all web service classes, Is there any way to capture the public method call from base class at runtime and then check if the attribute is being applied and then check the permission?
Thanks a lot!
Regards, John
Nicole,
It doesn't have to a Windows-integrated authentication scheme. That's
the beauty of the design, it allows for any implementation. One just has to
define the roles.
Because Windows authentication is being used, the easiest thing to do
would be to create windows groups based on the names of the web methods that
you want to call. Then, assign users to the groups that you want to have
access (if you can do this through AD, great, however, maintaining this
compared to setting an AccessCheck table on AD is going to be the same in
terms of overhead).
ASP.NET should be able to impersonate the user (set the impersonate flag
to true in web.config), and then you don't have to do anything regarding the
principal, it will just work.
Also, it will be easier to maintain the code, since you won't have to
code the call to check security every time your method is called (or every
time you create a new method), you just have to attribute the method and it
works.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message
news:el*************@TK2MSFTNGP14.phx.gbl... Not sure why, but I didn't even consider that this might have anything to do with the principal when I answered yesterday. That said, even if it is reasonably simple to swap out the principal for a web service, it's still not necessarily a great idea to do so. While using Windows-integrated authentication for web services is certainly simple, investing additional effort into tweaking the behaviour of a non-standard authentication mechanism probably isn't the best use of most folks' time... "Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:Or****************@tk2msftngp13.phx.gbl... Or (and I think this is the easiest one of all), just use a custom principal, and let Code Access Security take care of the rest. Basically, you implement IPrincipal, and set it as the principal for the thread that is doing the processing.
Attached is a console application which demonstrates how to use the PrincipalPermission attribute. Basically, there is an implementation of IPrincipal and the current thread is set to use that principal (you will have to do something different to have web requests use a certain principal, but Im sure you can do it). Then, you just apply the right attribute to your method, and the runtime will take care of the rest.
Try changing the IsInRole implementation to return something else, or the declaration of the PrincipalPermission attribute and the call to DoSomething will fail.
Hope this helps.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:O5**************@TK2MSFTNGP12.phx.gbl... Yes, but it's probably not as simple as you might have hoped. Here are the three main approaches:
1. Implement the check as a custom permission with a corresponding attribute (http://msdn.microsoft.com/library/en...rmissions.asp). This may be your best bet since you can presumably control whether the attribute assembly is registered as a trusted assembly.
2. Place the actual method work in objects that inherit from System.ContextBoundObject. This might interfere with your planned object hierarchy, as well as introducing an otherwise unnecessary performance hit.
3. Use a tool like XC# (http://www.resolvecorp.com/Products.aspx) to generate inline code that corresponds to your custom attribute.
If this truly is a security permission, #1 is probably the "cleanest" approach. Otherwise, #3 would probably offer the best compromise between design-time convenience and runtime performance.
HTH, Nicole "John Lee" <jo***@newsgroup.nospam> wrote in message news:ej****************@TK2MSFTNGP10.phx.gbl... Hi,
If I want to check permission on each public method of a web service, (assume the checking routine is ready to use and called AccessCheck) , one way of doing it is to call this AccessCheck on top of each public method, I want to implement it in different way but seems missing something -
I want to develop a custom attribute, let's say SecurityCheckEnabledAttribute with only Yes/No parameter, then create a base class for all web service classes, Is there any way to capture the public method call from base class at runtime and then check if the attribute is being applied and then check the permission?
Thanks a lot!
Regards, John
Thanks for your suggestion.
So you are saying DO NOT use Authorization Manager (AzMan) for role-based
security? Mapping User or Group directly to method call (creating security
group in AD) is the best way to go?
Thanks!
John
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:uh*************@TK2MSFTNGP09.phx.gbl... Nicole,
It doesn't have to a Windows-integrated authentication scheme. That's the beauty of the design, it allows for any implementation. One just has to define the roles.
Because Windows authentication is being used, the easiest thing to do would be to create windows groups based on the names of the web methods that you want to call. Then, assign users to the groups that you want to have access (if you can do this through AD, great, however, maintaining this compared to setting an AccessCheck table on AD is going to be the same in terms of overhead).
ASP.NET should be able to impersonate the user (set the impersonate flag to true in web.config), and then you don't have to do anything regarding the principal, it will just work.
Also, it will be easier to maintain the code, since you won't have to code the call to check security every time your method is called (or every time you create a new method), you just have to attribute the method and it works.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:el*************@TK2MSFTNGP14.phx.gbl... Not sure why, but I didn't even consider that this might have anything to do with the principal when I answered yesterday. That said, even if it is reasonably simple to swap out the principal for a web service, it's still not necessarily a great idea to do so. While using Windows-integrated authentication for web services is certainly simple, investing additional effort into tweaking the behaviour of a non-standard authentication mechanism probably isn't the best use of most folks' time... "Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:Or****************@tk2msftngp13.phx.gbl... Or (and I think this is the easiest one of all), just use a custom principal, and let Code Access Security take care of the rest. Basically, you implement IPrincipal, and set it as the principal for the thread that is doing the processing.
Attached is a console application which demonstrates how to use the PrincipalPermission attribute. Basically, there is an implementation of IPrincipal and the current thread is set to use that principal (you will have to do something different to have web requests use a certain principal, but Im sure you can do it). Then, you just apply the right attribute to your method, and the runtime will take care of the rest.
Try changing the IsInRole implementation to return something else, or the declaration of the PrincipalPermission attribute and the call to DoSomething will fail.
Hope this helps.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:O5**************@TK2MSFTNGP12.phx.gbl... Yes, but it's probably not as simple as you might have hoped. Here are the three main approaches:
1. Implement the check as a custom permission with a corresponding attribute (http://msdn.microsoft.com/library/en...rmissions.asp). This may be your best bet since you can presumably control whether the attribute assembly is registered as a trusted assembly.
2. Place the actual method work in objects that inherit from System.ContextBoundObject. This might interfere with your planned object hierarchy, as well as introducing an otherwise unnecessary performance hit.
3. Use a tool like XC# (http://www.resolvecorp.com/Products.aspx) to generate inline code that corresponds to your custom attribute.
If this truly is a security permission, #1 is probably the "cleanest" approach. Otherwise, #3 would probably offer the best compromise between design-time convenience and runtime performance.
HTH, Nicole "John Lee" <jo***@newsgroup.nospam> wrote in message news:ej****************@TK2MSFTNGP10.phx.gbl... > Hi, > > If I want to check permission on each public method of a web service, > (assume the checking routine is ready to use and called AccessCheck) , > one > way of doing it is to call this AccessCheck on top of each public > method, > I want to implement it in different way but seems missing something - > > I want to develop a custom attribute, let's say > SecurityCheckEnabledAttribute with only Yes/No parameter, then create > a > base class for all web service classes, Is there any way to capture > the > public method call from base class at runtime and then check if the > attribute is being applied and then check the permission? > > Thanks a lot! > > Regards, > John >
John,
I'm not exactly sure how the interaction between the WindowsPrincipal
and AD works. I believe there are some ties, but I am not positive. Since
you have IIS set up to impersonate the caller (and you will set up ASP.NET
as well), you will want the value of IsInRole to return true if they are in
a group that has the name of the web method.
The key is to assign the users in AD to a group that is recognized by
the windows principal. I believe this can be done (instead of using
AccessChecks).
CAS uses a role based scheme for providing security based on a
principal, assuming that if a user is in a group/role, then they have
permission to do something. You just have to change the information you
have about principals to reflect that.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"John Lee" <jo***@newsgroup.nospam> wrote in message
news:e3****************@TK2MSFTNGP09.phx.gbl... Thanks for your suggestion.
So you are saying DO NOT use Authorization Manager (AzMan) for role-based security? Mapping User or Group directly to method call (creating security group in AD) is the best way to go?
Thanks! John
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:uh*************@TK2MSFTNGP09.phx.gbl... Nicole,
It doesn't have to a Windows-integrated authentication scheme. That's the beauty of the design, it allows for any implementation. One just has to define the roles.
Because Windows authentication is being used, the easiest thing to do would be to create windows groups based on the names of the web methods that you want to call. Then, assign users to the groups that you want to have access (if you can do this through AD, great, however, maintaining this compared to setting an AccessCheck table on AD is going to be the same in terms of overhead).
ASP.NET should be able to impersonate the user (set the impersonate flag to true in web.config), and then you don't have to do anything regarding the principal, it will just work.
Also, it will be easier to maintain the code, since you won't have to code the call to check security every time your method is called (or every time you create a new method), you just have to attribute the method and it works.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:el*************@TK2MSFTNGP14.phx.gbl... Not sure why, but I didn't even consider that this might have anything to do with the principal when I answered yesterday. That said, even if it is reasonably simple to swap out the principal for a web service, it's still not necessarily a great idea to do so. While using Windows-integrated authentication for web services is certainly simple, investing additional effort into tweaking the behaviour of a non-standard authentication mechanism probably isn't the best use of most folks' time... "Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:Or****************@tk2msftngp13.phx.gbl... Or (and I think this is the easiest one of all), just use a custom principal, and let Code Access Security take care of the rest. Basically, you implement IPrincipal, and set it as the principal for the thread that is doing the processing.
Attached is a console application which demonstrates how to use the PrincipalPermission attribute. Basically, there is an implementation of IPrincipal and the current thread is set to use that principal (you will have to do something different to have web requests use a certain principal, but Im sure you can do it). Then, you just apply the right attribute to your method, and the runtime will take care of the rest.
Try changing the IsInRole implementation to return something else, or the declaration of the PrincipalPermission attribute and the call to DoSomething will fail.
Hope this helps.
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com
"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message news:O5**************@TK2MSFTNGP12.phx.gbl... > Yes, but it's probably not as simple as you might have hoped. Here > are the > three main approaches: > > 1. Implement the check as a custom permission with a corresponding > attribute > (http://msdn.microsoft.com/library/en...rmissions.asp). > This may be your best bet since you can presumably control whether > the > attribute assembly is registered as a trusted assembly. > > 2. Place the actual method work in objects that inherit from > System.ContextBoundObject. This might interfere with your planned > object > hierarchy, as well as introducing an otherwise unnecessary performance > hit. > > 3. Use a tool like XC# (http://www.resolvecorp.com/Products.aspx) to > generate inline code that corresponds to your custom attribute. > > If this truly is a security permission, #1 is probably the "cleanest" > approach. Otherwise, #3 would probably offer the best compromise > between > design-time convenience and runtime performance. > > HTH, > Nicole > > > > "John Lee" <jo***@newsgroup.nospam> wrote in message > news:ej****************@TK2MSFTNGP10.phx.gbl... >> Hi, >> >> If I want to check permission on each public method of a web service, >> (assume the checking routine is ready to use and called AccessCheck) >> , one >> way of doing it is to call this AccessCheck on top of each public >> method, >> I want to implement it in different way but seems missing something - >> >> I want to develop a custom attribute, let's say >> SecurityCheckEnabledAttribute with only Yes/No parameter, then create >> a >> base class for all web service classes, Is there any way to capture >> the >> public method call from base class at runtime and then check if the >> attribute is being applied and then check the permission? >> >> Thanks a lot! >> >> Regards, >> John >> > >
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Don Vaillancourt |
last post by:
Hello all,
Over the years as I design more database schemas the more I come up with
patterns in database design. The more patterns I recognize the more I
want to try to design some kind of...
|
by: sk |
last post by:
I have an applicaton in which I collect data for different parameters
for a set of devices. The data are entered into a single table, each
set of name, value pairs time-stamped and associated with...
|
by: Test User |
last post by:
Hi all, (please excuse the crosspost as I'm trying to reach as many people
as possible)
I am somewhat familiar with Access 2000, but my latest project has me
stumped. So, I defer to you...
|
by: rodchar |
last post by:
Hey all,
I'm trying to understand Master/Detail concepts in VB.NET. If I do a data
adapter fill for both customer and orders from Northwind where should that
dataset live?
What client is...
|
by: tshad |
last post by:
Many (if not most) have said that code-behind is best if working in teams -
which does seem logical.
How do you deal with the flow of the work?
I have someone who is good at designing, but...
|
by: roN |
last post by:
Hi,
I'm creating a Website with divs and i do have some troubles, to make it
looking the same way in Firefox and IE (tested with IE7). I checked it with
the e3c validator and it says: "
This...
|
by: JoeC |
last post by:
I have a question about designing objects and programming. What is the
best way to design objects? Create objects debug them and later if you
need some new features just use inhereitance. Often...
|
by: |
last post by:
I have a question about spawning and displaying subordinate list controls
within a list control. I'm also interested in feedback about the design of
my search application. Lots of code is at the...
|
by: neelsmail |
last post by:
Hi,
I have been working on C++ for some time now, and I think I have a
flair for design (which just might be only my imagination over-
stretched.. :) ). So, I tried to find a design...
|
by: indrawati.yahya |
last post by:
In a recent job interview, the interviewer asked me how I'd design
classes for the following problem: let's consider a hypothetical
firewall, which filters network packets by either IP address,...
|
by: DolphinDB |
last post by:
Tired of spending countless mintues downsampling your data? Look no further!
In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM).
In this month's session, we are pleased to welcome back...
|
by: Vimpel783 |
last post by:
Hello!
Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
|
by: ArrayDB |
last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
|
by: PapaRatzi |
last post by:
Hello,
I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Defcon1945 |
last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
|
by: Shællîpôpï 09 |
last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
| |