By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,850 Members | 972 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,850 IT Pros & Developers. It's quick & easy.

What is the ideal platform?? only .Net Framework or .Net Framework with SDK

P: n/a
Hi All
We are facing problems like unable to cast object of a type to same type while calling Activator.GetObject() function. But the same problem disappears when Visual Studio .Net in installed on the server. I have gone through a lot of articles where people have talked about debugging in production enviornment. But in almost all case they have assumed that SDK along with .Net Framework is there. I am curious about what is ideal production enviornment platform. Only .Net Framework is sufficient or .Net Framework SDK should also be present

If some body can through some light on this then it will be a great help to us as we are trying to debug the problem since almost a month

Thanks in anticipation

Arvind Kumar Maury
Senior Member Technical Staf
HCL Technologies
Jul 21 '05 #1
Share this Question
Share on Google+
3 Replies

P: n/a
Hi Arvind,

When you are deploying using the deploying and setup from, the right
..Net framework version should normaly be sufficient.

Although I think it is better to do a windows update on the client to be
more sure.

I hope this helps?

Jul 21 '05 #2

P: n/a
Hi Cor
Thanks for the reply
Actually we are compiling our code written in C# using makefiles where nmake is being used for compilation. Right now we are doing deployment manually. We are hosting components on IIS 5.0 and installing only .Net Framework on server.
We are having scenerio where a .Net client calls a component hosted on IIS using .Net Remoting. Sometimes this calls succeed but sometimes call from .Net client fails while getting remoting object using Activator.GetObject() API. We have tried to debug the cause but found that Activator.GetObject() API is returning the object with Type we have requested for(say X). But when we typecast it to the X, it fails with exception Unable to cast object of type X to X

The same problem disappears when we install Visual Studio .Net on the server

Can you through some light on it

Arvind Kumar Maury
----- Cor wrote: ----

Hi Arvind

When you are deploying using the deploying and setup from, the righ
..Net framework version should normaly be sufficient

Although I think it is better to do a windows update on the client to b
more sure

I hope this helps


Jul 21 '05 #3

P: n/a
Hi Arvind,

The greath advantage from using managed code should be that there never
would be anymore problems as you have now.

Unless you are using non managing code in your programs, than you have to do
yourself that terrible job to find out what dll's are extra needed (as done
by the deployment and setup).

One thing is better, you are almost sure that it are dll which has to do
with your API and not with the managed code because that is in the
framework. (Not the Com referenced, that you have to check if it is complete
on the user computer and allowed to deploy)

I have no better answer than lets hope that in future all is managed code
and this kind of problems are gone.

Jul 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.