|
Hi,
Having traditionally written C++ windows applicatons for a number of years, I am looking forward to geting to know the .NET technologies.
While starting to read about what is available the first thing that springs to mind is how are these applications deployed, what OS's support this.
There is a lot of talk about cross-platform compatibilty but does that mean when you are deploying your application on non-.NET compliant systems e.g. I assume win95, win98,ME,non-Microsoft OS's then you install the necessary .NET components?
Could anyone point me in the direction of any articles that addresses this area.
Thanks
Neil
|
|
|
|
|
Best place is on MSDN in the Deploying .NET Framework Applications*.
If you have high level questions about .NET then msdn.microsoft.com/net* is the place to start.
About the cross-platform compatibility; the platform you want to deploy to will have to have a .NET framework written for it. The MONO project is doing this for Linux so that you can run .NET apps on Linux. I am unsure though about other versions of Windows or other OSs.
Hope that helps 
*links open in current browser window
regards,
Paul Watson
Bluegrass
Cape Town, South Africa
"The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
"In other words, the developer is dealing with an elephant, the accountant is dealing with a bunny rabbit." by Stan Shannon - 16/10/2001
|
|
|
|
|
The .NET Framework will be available for Windows 95 through XP. Some installation packages such as InstallShield Developer and Wise Installer allow you to package a "merge module" for the .NET Framework, thus ensuring that it is installed on the target machine if it is not already there.
MSDN is a great resource and all of the technical content is available free at http://msdn.microsoft.com
Cheers!
Colin Bowern, Consultant
Enterprise Platform Solutions
Microsoft Services (Canada)
|
|
|
|
|
Hi,
If anybody has worked on returning NameValueCollection from webservice, I hope you might have come accross this typical error message.
You must implement the Add(System.String) method on
System.Collections.Specialized.NameValueCollection because it inherits from
ICollection.
Please let me know if anybody has a solution
Pooran Prasad R.
Itreya Technologies Pvt. Ltd.,
Bangalore, India
pooran.prasad@itreya.com
|
|
|
|
|
We are seeking people knowledgeable in all facets of .NET for a short-term freelance technical documentation role. Role involves creating tests and testing methods to measure knowledge of the subject matter. For serious inquiries send an email testcoordinator@techprofiles.com
|
|
|
|
|
I've played around with the Soap Toolkit a bit and i'd like to take a look at the .Net soap stuff but I can't seem to find any C++ SOAP examples for .Net.
What I need to do is build a C++/MFC windows app that can talk SOAP. Not only does it need to understand soap but it needs to be able to handles complex types from a SOAP service writen in Java. The Java side serializes a java class and I need to be able to deserialize it.
any pointers or examples? I can find nothing on the ms site.
thanks
mike
|
|
|
|
|
i try to use gdi+ in my atl dll project. but it was failed when i try to exit my process because the gdiplusshutdown fuction is failed. what can i do?
|
|
|
|
|
We had this problem on a machine that we'd not installed the full platform SDK on using MFC, and we found that just failing to shut it down still worked OK. GDI+ is a COM object itself, so I see no reason why you should have trouble running it in ATL.
Christian
As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet.
Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.
|
|
|
|
|
i really have not installed the full platform SDK. but i can use gdi+ normally when i useing MFC. but it is really failed when i called the function gdiplusshutdown in my ATL DLL project. maybe i need installed the full platform SDK? i will try
|
|
|
|
|
If you're following Christian's article, there's a little mistake that causes LNK2001 on GdiPlusShutdown. Change your ULONG_PTR typedef to
typedef ULONG_PTR ULONG;
--Mike--
http://home.inreach.com/mdunn/
"Listen you footwarriors, can you hold down a bit with the firing? I've just got three impromptu weddings breaking out behind me!" -- Arthur Dent
![Heart | [heart]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/love.gif) your ![Green Alien | [Alien]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/alien.gif) with ![Good Stuff | [The good stuff]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/vegemite.gif) and ![Beer | [beer]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/beer.gif)
|
|
|
|
|
I am in the design phase of a new product. Do I use good old MFC or use it as a good opportunity to get to know C# under .net ? The problem is two fold. First of all , this code must work with 95 . And secondly it will have a service / minimised app part and gui part. So , what platforms are .net going to run on ?Is it practical to use it to write services , if not then how small a footprint in memory is the runtime if I have to use a minimised app instead ?
|
|
|
|
|
I believe that only 98 and ME and NT/2000/XP are going to be supported with .NET. Microsoft is trying to slowly phase out 95 support. Most Win95 systems don't tend to have the kind of machine that .NET is going to need.
My .NET Visual Studio Beta 2 allows me to build a Windows service in C#, I haven't played with it much but it seems to be useable.
Whether you choose C# or MFC is a difficult choice. When do you need your app to be finished by? If it is sometime this year, I'd forget C#. I doubt that Visual Studio .NET will be ready before the end of the year and trying to develop a full product with a BETA product makes life so much harder.
At the moment I'm sticking with the good old MFC/WTL/ATL technologies. I'm itching to start writing C# but my customers aren't likely to be using .NET in the near future.
Michael
|
|
|
|
|
Hi all
I have a c# libary which includes a COM componant that fires events and registers a remote object. using this libary from a Simple winforms program(so that I see that the events are being called) I don't have any problems. using another simple console based based program to debug the remoting, I also have no problems. However once I use an ASP.NET web page with the remoting I seem to stop recieving some of the events from the COM componant. i.e event 'foo' is recieved sometimes but not others? After loading the ASP.net web page I also start to get the same problem with the initial test program. From what I can see, the problem only seems to happen once aspnet_wp.exe is running.
Has anyone else had similar problems? If so has anyone found any way to fix it, or a way around it?
I am running Windows 2K, VS.Net Beta2, 1Ghz Athlon and 256 Meg Ram.
Thanks
Martin
|
|
|
|
|
I installed .Net,and I found the component writed with VB was correct while debug step by step,then I make the dll.But it does not work correct.(In one method of this component ,I called one function of another dll just for unzip files.)
If this is caused by .net?
sandos
|
|
|
|
|
Where can I download free beta2 version of Visual Studio .NET?
|
|
|
|
|
You cannot download it. Get yourself the septmber issue of msdn magazine. There is a dvd included with the framework and visual studio .NET and some extra's. It will cost you about 6 bucks.
yours,
Filip
|
|
|
|
|
DVD being the operative word there! Call me a nerd but I don't have a DVD drive on my development box. And I wasn't planning on installing one, but Microsoft finds it necessary in their benevolant wisdom to build these monoliths of apps. It's !@#$#$ huge hence it is on a DVD...
On a seperate rant (look for it) I'm can't get the %$@%@! thing to install. I twidle my thumbs while it runs thru its course, then it hangs at the very end. No usable information in the errorlog.
|
|
|
|
|
Hi,
what exactly is .NET?
Is it a new Developer Kit and it is coming instead of Visual Studio? Or is Visual Studio 7 is coming sometimes, too?
I think .NET would be a new Dev-Kit and the Visual Studio 7 wouldn´t be released, because now .NET is the Dev-Kit, or what?
???
|
|
|
|
|
|
.NET is a new framework or foundation that Microsoft have put together. To fully explain it would require at least 30 markerters so I recommend you visit MSDN and read up on it.
VS7 is now called VS.NET i.e. Visual Studio .Net. It is a development environment for creating .NET applications. Currently it is in Beta 2 stage and will be released in October (I have a case of beer resting on that!). Read up on it at Visual Studio.
regards,
Paul Watson
Bluegrass
Cape Town, South Africa
"We would accomplish many more things if we did not think of them as impossible."
- Chretien Malesherbes
|
|
|
|
|
Hi there,
I am not very informed on .NET. I was wondering what will happen to MFC or
COM and DCOM and COM+ in .NET.
Will any of them be there when .NET comes
around?
|
|
|
|
|
I'm not much informed either, but the current MSJ addresses this with an article on Interop - this is a Runtime Callable Wrapper that enables .NET based apps to access COM based stuff and vice versa.
I guess that covers COM+ and DCOM too. (Though I personally think COM is/was too COMplicated and this is yet another level of COMplexity added).
MFC survives as well - there's some changes to how things are written (more templated code) but I think the MFC stuff is 'off and to the side' in the .NET scheme of things. (Here's a tip though - test your CObList code for const correctness )
Just 2 centavos worth...
oops
...did I say MSJ? I mean MSDN magazine...
oops 2
Arrgh - no - the RCW is from .NET to COM, and the COM-callable Wrapper (CCW) is from COM to .NET... sigh... its all too COMfusing...
|
|
|
|
|
I have been trying to use classes from a managed dll (written with C#) from an MFC app using MFC 7. After resolving the problems compiler switches, I am left with the C3828 compile error on the line:
MyCSClass::CSClass *cs = new MyCSClass::CSClass();
Is is impossible to do this with MFC? Thanks in advance for any help.
|
|
|
|
|
From a look at the docs, you might be ok in a release build.
VC won't allow placement new when creating instances of managed types - and the debug new operator, redefined to enable allocation tracking, runs afoul of this.
A work-around is to undef the new operator temporarily -
#pragma push_macro("new")
#undef new
...
#pragma pop_macro("new")
|
|
|
|
|
I just downloaded CodeSwap, this Visual Studio .NET add-in. It's like Napster for code. I searched code using keywords and got small, simple samples that I could use. Pretty cool!
Anyone can post their code to this shared server. It has ratings and all the other things you'd expect.
Has anyone else checked it out? It's at www.vscodeswap.com.
Dave Murdock
Point Richmond, CA
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
