.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

32 bit and 64 bit OCX both loaded into managed application (Any CPU)

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :WPF

I have a managed application (Any CPU) which is a windows form application josting an ActiveX control. The ActiveX control is written in MFC and is compiled for both x86 (32 bit) and x64 (64 bit). When I run up the program, process Explorer shows the following:

Process                                    PID       Type         Handle or DLL

WindowsFormApplication1.exe   4004      DLL           D:\Development\64Bit\TheAxControl.ocx

WindowsFormApplication1.exe   4004      DLL           D:\Development\32Bit\TheAxControl.ocx

WindowsFormApplication1.exe   4004      Handle       D:\Development\64Bit\TheAxControl.ocx

The same thing happens for targeted x86 and x64 builds. Now, I have read that 32 bit in-process DLLs cannot be loaded into 64 bit processes and vice-a-versa (let's call this paradigm A). That they should meet at a process boundary with some sort of IPC. In

View Complete Post

More Related Resource Links

Error Handling: Throwing Custom Exception Types from a Managed COM+ Server Application


Exception handling semantics in .NET are based on type, so you can create custom exceptions that have their own properties and methods. In .NET, exceptions are first-class citizens, and since they're the built-in error handling mechanism, all .NET-compliant languages must support exceptions. In addition, COM+ services are available to .NET code as Enterprise Services, so you can leverage exceptions in your Enterprise Services design.In this article the author describes custom exceptions, throwing exceptions across COM interop boundaries, and working with Enterprise Services.

Bob DeRemer

MSDN Magazine March 2004

.NET CLR Profiling Services: Track Your Managed Components to Boost Application Performance


The Microsoft .NET platform provides you with a rich set of services for building profilers and application monitors for applications targeting the Common Language Runtime (CLR). These services expose runtime events that occur during the execution of a .NET application. They can be used to obtain information about managed code being executed under the runtime. This article describes the .NET CLR Profiling Services and shows how to use the services to build a simple profiler that will provide hot spot information for any .NET application. The sample profiler can easily be modified to suit other profiling and monitoring needs.

Anastasios Kasiolas

MSDN Magazine November 2001

C# and the Web: Writing a Web Client Application with Managed Code in the Microsoft .NET Framework


When the author wanted to build a middleware Web client to connect to other applications over the Internet, he realized that the XMLHttpRequest COM object was not sufficient for his purposes. In order to build a Web client using managed code, the author had to use the HTTPWebRequest and HTTPWebResponse classes provided by the Microsoft .NET framework. These classes are used in the sample project as a substitute for the less powerful XMLHttpRequest COM object, allowing the author to build a full-featured Web client. They also take advantage of all the benefits that the CLR and managed code have to offer.

Avi Ben-Menahem

MSDN Magazine September 2001

Managed Metadata Service - No EMM application proxy can be found



I have Managed Metadata Service configured with the default language German and the target Content Hub it also in German. When I try to publish a content type i got this error "cannot check for changes because no emm application proxy can be found". Any ideea?


Issue using Managed Metadata with custom fields in the User Profiles application


Hi there,

I've created several custom properties in my User Profile Application.

I've also created several Term Sets in the Managed Metadata service application Term Store for use with these custom properties. Some of the Term Sets contain terms and have a closed submission policy whilst others have an open submission policy.

If the user hasn't already populated any of these custom fields in their profile, when they click on the Edit My Profile link from their My Site Profile page everything seems okay (for the first time).

The user is then able to successfully select values for these custom fields - the metadata is available. They can click on the "tag" icon to select values, or start typing and the suggestions appear. They are also able to enter new values into custom property fields where the term set is open to submission.

If they then Save and Close then go back into Edit My Profile, often not all of the existing data is populated in the metadata custom fields. On different occasions different fields may be blank. Sometimes this is accompanied by the error "Message from webpage / The server method 'ValidateTerms' failed", but not always.

Has anyone else tried this or have any suggestions are to what the issue might be?

Thanks in advance.

Managed Metadata Service: Cannot check for changes because no EMM application proxy can be found


We have a managed metadata service with two owners. Both of them can't change anything to the term store anymore. The moment they try they get access denied:

The user doesnt have enough permissions. When looking into the log of SharePoint i found the following message:

Cannot check for changes because no EMM application proxy can be found

When I try to add another administrator using the Install_Admin account (who is farm admin) I get the same message that the user doesnt have enough permissions.

Our term store is setup in multiple languages with Dutch being the primary one.

Any help much appreciated.


Remote monitoring and diagnostics for managed application


Please advice me...

I have a need to monitor (collect diagnostics) an application deployed, as a Windows Service, to over 40,000 (yes, forty thousand machines). Majority of the machines does not have standard tools like Visual Studio remote debugger, etc that are used for such purpose.

Also, I am not sure if WCF can be used as I am concerned about security - please enlighten me about pros and cons of having a WCF-Service-In-a-box approach. If so, what is the best binding.

Can WinRM be used to interact with a WCF NetPipe listening in the application? Any, article on this would be useful? What are the security aspects that should be focussed in this scenario.

Thanks in advance


Service Application Connection: Managed Metadata Service is inaccessible


 Hello all,

I have published the MMSA in one farm so it can be connected to and consumed by another farm. The publishing farm URL is https (SSL) and the consuming farm is http (Non-SSL). The connection to the MMSA shows in Central Admin as succesful, however when I try to open the Managed Metadata in the term store in the consuming farm I get the following error:

"The Managed Metadata Service is inaccessible because the current web application has not been granted permissions to access it."

I followed all the steps in technet, including the certificate exchanges and the publishing farm MMSA has granted the consuming farm full control.


Any clues? Can a farm with SSL publish service applications to non-SSL farms?


Managed Metadata Service Application Problem



I've been trying for a whole day to configure managed metadata services on a windows server 2008 R2 environment but I keep getting this error:

The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.

I've tried searching for a resolution and here's what I got:

  1. Change the application pool account / Check that the pool is running.
  2. Download hot fixes KB981002 and KB976462.
  3. IISRESET / Restart the server.
  4. Ensure that Managed Metadata service is running.

The third solution worked for me in my development environment which is Windows 7, but I couldn't get it to work in Windows server 2008 R2 which is the production environment.

Any help would be appreciated :)

Microsoft's Collaborative Application Markup Language (CAML) Loop

discovered an interesting error recently while working with Microsoft's Collaborative Application Markup Language (CAML) that, surprisingly, had received no ink. Partly what surprises me about this is that the error may require you to rewrite large sections of your code if you haven't previously considered this SharePoint limitation. I'll start with some context, but first of all the error is:

Integrating a Legacy Web Application in SharePoint

This month we will continue with the theme of deploying Microsoft's SharePoint as a company intranet by describing a method for integrating a legacy Web application inside a SharePoint site.

In many companies the intranet site is not just a home page with announcements. It houses Web applications used by many different departments. In last month's article, I built a page to search the employee table in Northwind (the sample database included in Microsoft's SQL Server). This month, I will move the Web pages used to add/remove records from the table into the SharePoint intranet.

MVC architecture in ASP.Net using C# and Microsoft Data Access Application block

The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes [Burbeck92]:

Model. The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller).

View. The view manages the display of information.

Controller. The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate.

High-Performance .NET Application Development & Architecture

It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. Pre-.NET strategies and design guidelines still effective now were developed with Microsoft's DNA (Distributed interNet Application) platform. This model successfully served the purpose of architecting N(any number of)-Tier (levels) applications. In its basic sense, as in most robust, distributed applications, you'll architect 3 main layers or Tiers: presentation, business rules and data access.

Application architecture in asp .net

Application Architecture is the most important process of developing a good application. Some people tends to jump into coding without any architecture laid. Later we see those people changing the architecture and finally the application had to be developed from the scratch with the correct architecture.

In this article I will describe some details about how you can improve the architecture of you application. This article is targeted to the beginner's audience.

Improving Application Performance in .Net

Application performance has always been a concern for Web Application developers. This article contains guidelines and tips for maximizing application performance in ASP.NET.

Logic behind N -Tier Application Development

In the arena of application development, developers all over the world use various programming languages, technical processes, and technical tools. While using number of technical & non technical elements the processes or methods become complex, for simplification of the application development process, developers use various techniques such as dividing the application architecture into layers or parts. In the professional & technical language this separation or division process is called N-Tier Application Development process, where "N" stands for number and "tire" stands for layers or parts.

How to create 3 tier application using LINQ

As you know that in 3 tier architecture there are three layers

User interface layer. (Is our Form in Windows application and .aspx page in Web application)
Data Access layer. (Which provides interface between Business logic layer and Database)
Business Logic layer.(Which stores your application logic)
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend