Wrox Programmer Forums
Go Back   Wrox Programmer Forums > C# and C > C# 1.0 > C#
|
C# Programming questions specific to the Microsoft C# language. See also the forum Beginning Visual C# to discuss that specific Wrox book and code.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the C# section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old March 18th, 2007, 08:08 PM
Registered User
 
Join Date: Mar 2007
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default Namespaces and DLLs

Hi all, sorry if this question is too newbie, but it is because I am c# newbie :)

Is there some 'penalty' to putting classes in different namespaces? Like runtime delays and such?

Let's, for example purpose, assume I have three classes. Each class does some things and each eventually needs data generated by the other ones.
Currently I have them all on the same .exe and the same namespace.
For organization, I am considering throwing each to a separate namespace. On the ideal part of things I am thinking in putting each different namespace on it's own DLL file, but I don't know if I will damage runtime performance by doing it so.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Can I use two dlls with same name but prakashrams ASP.NET 1.0 and 1.1 Basics 1 November 29th, 2006 11:26 AM
Issues with DLLs ninel .NET Framework 1.x 1 August 18th, 2006 11:20 AM
Using DLLs in VB 6 gjc VB How-To 2 September 7th, 2005 03:47 AM
debugging DLLs in C# grs General .NET 0 December 20th, 2004 07:17 AM
Need to use VC++ Dlls Incredible Flash (all versions) 1 November 29th, 2004 11:35 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.