I notice that the contect in these doesn't have an executionProperties property. I keep havind to convert activities across to native just for this feature.
Is there a way to access this?
View Complete Post
In this article, the author delves into some commonly used ways of writing data access code and looks at the effect they can have on performance.
MSDN Magazine August 2009
This month's column continues the discussion around code access security in WCF and partially trusted services.
MSDN Magazine July 2008
Here we discuss code-access security in Windows Communication Foundation (WCF) and present a solution for enabling partially trusted clients for WCF services.
MSDN Magazine April 2008
Unlike role-based security measures, code access security is not based on user identity. Instead, it is based on the identity of the code that is running, including information such as where the code came from. Here Mike Downen discusses the role of code access security (CAS) in .NET and outlines some key new features and changes in CAS for the .NET Framework 2.0.
MSDN Magazine November 2005
Rich clients employ many of the features and conveniences of the operating system they run on, and the list of these features has been growing since the dawn of the PC. But as apps have migrated to the Web, the trend towards increasing client-side functionality has ground to a virtual halt. There are several reasons for this; chief among them are security and deployment problems. But that's all about to change. With the .NET Framework, you can participate in building the distributable rich client of the future. In this article, the author enumerates the pertinent features of .NET that will allow you to build safe, easily deployable controls. The features discussed include managed code, code access security, versioning control, Windows Forms classes, and isolation.
MSDN Magazine June 2002
Component-based software is vulnerable to attack. Large numbers of DLLs that are not tightly controlled are at the heart of the problem. Code access security in the Common Language Runtime of the Microsoft .NET Framework addresses this common security hole. In this model, the CLR acts as the traffic cop to assemblies, keeping track of where they came from and what security restraints should be placed on them. Another way the .NET Framework addresses security is by providing preexisting classes which have built-in security. These are the classes that are invoked in .NET when performing risky operations such as reading and writing files, displaying dialog boxes, and so on. Of course, if a component calls unmanaged code, it can bypass code access security measures. This article covers these and other security issues.
MSDN Magazine February 2001
There is a scenario that the custom NativeActivity need to access to params or args defined in parent activity. What i have done as below
protected override void Execute(NativeActivityContext context)
WorkflowInstanceProxy proxy = context.GetExtension<WorkflowInstanceInfo>().GetProxy();
Activity root = proxy.WorkflowDefinition;
Activity rootChild = WorkflowInspectionServices.GetActivities(root).ElementAt(0);
EditingContext ec = new EditingContext();
ModelTreeManager mtm = new ModelTreeManager(ec);
ModelItem modelItem = mtm.Root;
ModelProperty c1 = modelItem.Properties["Variables"];
ModelItemCollection c2 = c1.Collection;
dynamic c3 = c2.GetCurrentValue();
string value = c3.Get(context);
Apparently it is not possible to access to external params with local context so the error prompt "An activity can only access its own implementation variables."
My question is how to get it ? Is there another easy way to do so ?
Could someone help me with the following issue, please?
- Windows 2008 R2 server hosting both MVC2 web application and WCF service for it;
- users connect to the web application which gets all data from the WCF services;
- WCF services are resused by several other applications (WinForms based) which work fine and have never experienced any security related problems;
- MVC2 uses impersonation (<identity impersonate="true"/>) to connect to WCF services, so we have single security boundary for both web and winforms clients (which are out of scope of the problem);
- both MVC2 web application and WCF services share the same ASP.NET v4.0 DefaultAppPool application pool, running under NetworkService identity;
- all users, user PCs and servers belong to the same AD domain, which is a part of global corporate tree;
- all unhandled exceptions are automatically caught by the web application and forwarded to application developers' e-mail box;
- WCF binding setup in web application:
<binding name="WSHttpBinding_BifrostServices" closeTimeout="00:10:00"
openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"