|
If you like Wise, Wise for Windows Installer works with .NET as well; I just downloaded the eval and had my component installed into the GAC in no time.
It took me about 10 minutes to figure out where it put my setup program tho (crazy "bug" where click the drop down for the look in directory takes you straight to the desktop.)
James
Sonork ID: 100.11138 - Hasaki
"Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick.  " - Michael P Butler Jan. 18, 2002
|
|
|
|
|
Would you please send me the link you download it/
Thanks
Mazy
You can find a solution (even a foolish one) for all problems (even big ones)
|
|
|
|
|
Sure can 
http://209.104.132.210/WfWIEval.exe
[Edit: The reason I'm giving a link right to the exe rather than to the wise evaluation form is that the site is having troubles; I keep getting an error trying to load the homepage 
James
Sonork ID: 100.11138 - Hasaki
"Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick. " - Michael P Butler Jan. 18, 2002
|
|
|
|
|
Where can I download the Smart Device Extensions for Visual Studio .Net?
For some reason I am not able to find it. It would have been nice if it came with VS .NET Enterprise Arch install, or did I miss it?
Kind regards,
Tim
|
|
|
|
|
With the PDC 2001 release it was included on a separate CD. Is it the same for EA?
James
Sonork ID: 100.11138 - Hasaki
"Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick. " - Michael P Butler Jan. 18, 2002
|
|
|
|
|
It appears that the Smart Device Extensions are not fully available yet. It did not come with the official release of Visual Studio .NET
Kind regards,
Tim
|
|
|
|
|
Problem 1:
If I temporarily hide an MDI child Form and then show it again like this...
myForm.Hide ();
...
myForm.Show ();
...then the Location is chosen at random as if this was the very first time the Form is displayed.
I work around the problem like this:
Point priorLocation = myForm.Location;
myForm.Show ();
myForm.Location = priorLocation;
But that causes a gross visual blunder as the window is initially displayed in a random position and then jumped to its new position.
I tried using the underlying ShowWindow API on the window handle and that solves the location problem but unfortunately does even nastier things to the entire .NET Form internal state. (Windows don't show as being active, etc.)
Does anybody have a technique for preserving the location of an MDI child Form that does not have a visual glitch?
Problem 2:
Maybe this is not related but when I (re)Show a child Form, an ActiveX object embedded on that form likes to draw itself on the desktop instead of in the child window. Any ideas here?
Eric Newhuis
enewhuis@futuresource.com
|
|
|
|
|
This looks like it might be a bug with MDI Child forms. An interim solution is to set the MDI Child forms StartPosition property to FormStartPosition.Manual. The only disadvantage is that any new windows that come up are started in the upper left corner (unless you provide a new position for them).
The placement isn't actually random, its Windows default location for when a new form is opened.
No idea for Problem 2 since I don't have any experience with AX on winforms.
HTH,
James
Sonork ID: 100.11138 - Hasaki
"Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick.  " - Michael P Butler Jan. 18, 2002
|
|
|
|
|
Hi,
There is a lot of talk these days about the .NET vs J2EE thing. I have taken a look on both sides and I was wondering if the COM+ architecture is still a fundamental thing in .NET for distributed computing?
(Yes I know, .NET eventually emerged out of COM+2.0 or NGWS or whatever)...
But for distributed computing, have things changed from COM+ ? Is there such a thing as J2EE that offers server-side containers being statefull (<-> COM+, as far as I remember?), how slick and integrated is everything?
They must be a lot more elegant right now, can someone please give me a pointer to information in msdn about that?
thanx for reading, cursing and flaming 
|
|
|
|
|
Com+ is fundamental in distributed computing, whether you use .NET or not, the services provided by Com+ are the fundamental thing (like distributed transactions, object pooling, the easy thread development architecture, etc..), which were not supplanted by any new technology (yet).
In .NET you can write Serviced Components (this are the Com+ components that we write today in Visual C++, Visual Basic,..), these will run inside Com+ and can take advantage of the services provided by it.
Right now there isn't support for statefull components, in the sense of J2EE, but microsoft it's working on a new technology that permits something like this, I can't remember the name (something like "Object Space" or so).
The idea of statefull componentes is just the opposite to the spirit of Com+, where one of the rules is "do not maintain state" (see Transactional COM+: Building Scalable Applications by Tim Ewald http://www.amazon.com/exec/obidos/ASIN/0201615940/qid%3D1013822174/ref%3Dsr%5F11%5F0%5F1/103-4000867-4379823)
Hope this clarify a bit.
(and sorry about my english
Andres Manggini.
Buenos Aires - Argentina.
|
|
|
|
|
I use VC 6 + MFC to develop standalone 'traditional' mfc based apps. Along with a lot of others I expect. I'm not in the slightest bit interested - at least not yet - in the .net runtime platform stuff and all that internet linkage that seems to be stuffed in there and that MS is pushing as the latest and greatest.
But I am interested in a compiler update and new release of mfc that can be used for traditional Windows app developers, especially if it has more bugs fixed, better support for Windows xp user interface etc etc.
So would VS .net do anything for me? Or am I locked into VS6?
Can anyone comment on the reliability, bugginess of vs .net?
|
|
|
|
|
VC.Net has a *TON* of *NEW* features:
New IDE for generating classes, events.
New MFC classes, some classes now templatized.
New compiler/link switches.
New C++ extensions.
I've ported some of our existing projects into the VC++ .NET IDE and compiled them without any problems. The compiler certainly is better/stricter than VC 6.0. in a nutshell if your're a VC++ developer you should be using VC++ 7.0 (.NET).
Normski. - Professional Windows Programmer
|
|
|
|
|
Hi Almond 
Well, How about speed in compiled program by .NET and new Win32 library ?
My month article: Game programming by DirectX by Lan Mader.
Please visit in: www.geocities.com/hadi_rezaie/index.html
Hadi Rezaie
|
|
|
|
|
Hadi_Rezaie wrote:
Well, How about speed in compiled program by .NET and new Win32 library ?
new Win32 library? 
Normski. - Professional Windows Programmer
|
|
|
|
|
Norm Almond wrote:
I've ported some of our existing projects into the VC++ .NET IDE and compiled them without any problems. The compiler certainly is better/stricter than VC 6.0. in a nutshell if your're a VC++ developer you should be using VC++ 7.0 (.NET).
What about the target system ? Do you need W98 or better ? Any other thing to look for ?
I tried an app with MFC as a shared library and had some problems in the target system. Where to look for information about redistributing DLL's ?
|
|
|
|
|
Anyone had any trouble using VC6 and VS.NET on the same machine?
I won't install VS.NET till at least 5 people say it works without a hitch.
Johannes
|
|
|
|
|
I have the RC1 and VS6 on my computer and they both seem to work. I don't have the RTM yet.
--
Peter Stephens
|
|
|
|
|
Works fine for me on two machines.
|
|
|
|
|
Works fine here, I even installed VC6 after VS.NET without any problems.
James
Sonork ID: 100.11138 - Hasaki
"Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick. " - Michael P Butler Jan. 18, 2002
|
|
|
|
|
They coexist just fine.
Tim Smith
Descartes Systems Sciences, Inc.
|
|
|
|
|
I have VC6 and VC.NET RC and they coexist just fine. This is post no. 5, so you may proceed
|
|
|
|
|
I have VS6 and VS.NET beta 2.0 running together fine. For a short while I also had MS Embedded tools [VB and VC] 3.0 installed. All this is on Win2K server SP 2.0
Regards
Nish
Sonork ID 100.9786 voidmain
www.busterboy.org
If you don't find me on CP, I'll be at Bob's HungOut
|
|
|
|
|
Thank you all. It seems there shouldn't be any problems.
Johannes
|
|
|
|
|
A voice of dissention from this .Net love fest.
I was able to install both VC6 and VS7 on the same machine. However, VS7 did not support a few of our project configurations with SourceSafe. I also had problems with libraries; in short some libraries build for VC6 would run with VS7, but not the other way around.
On top of that, I encountered so many bugs, aggravating quirks and just plain idiotic interface elements in VS.Net that I just uninstalled it. Whatever benefit a new compiler and linker might provide could not overcome the aggravation of working with VS.Net.
(Try converting a project, or rather "solution", with a base library and several executables dependent on that library but not each other. You will be both amazed and baffled at how the "solution" interprets "dependencies." Then try a build/debug cycle. This was the moment I started swearing very loudly and decided I'd had enough.)
|
|
|
|
|
Hello,
I have this private assembly, and I want to ensure that it can be used only
in my application. I have signed the assembly using strong name key pair
that I generated.
But when I am calling it dynamically (i.e. Assembly.Load) how can I ensure
security, i.e. check for the public key, so that only my application will be
able to use it coz only my application knows my public key?
Any ideas?
- Tariq
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
