I'm trying to make more use of namespaces and giving my project a more rigorous design, as it has been getting pretty messy.I was wondering,before I get started, is there a standard convention for the names and organization of namespaces?For instance,for a 3-tier program, should there always be a "UI", "Business",and "DataAccess" namespace (and is this what they're typically called)?Or should I just organize the project as I see fit?
I have 2 projects, one built in VB.NET and another in C#.NET. I want to use certain functionality of VB.NET into C#.NET and hence I have added the dll file of VB.NET solution into C#.NET as a reference by browsing the dll from my system. Say dll name for VB.NET is myData.dll. In my C#.NET project I am trying to declare it as a namespace i.e. "using myData;" and its giving me an error of "Type or namespace name could not be found"
I have a vb.net 3.5 class library project that needs to reference two assemblies that have the same namespace. We have two third party dll's in which one is version 5.1 and the other is version 6.1. They have the same dll filename and they utilize the same namespace and functions/class names. The project needs to use one or the other depending on a specific situation. I've investigated up on a c# process that uses the "extern alias" feature to pull in the different assemblies.
[URL]
What use is the Aliases property of assembly references in Visual Studio 8.It seems that this feature isn't fully available for vb.net. Things I've Tried I've renamed the 2nd dll and added both references to my project. At this point I get tons of: 'blah' is ambiguous in the namespace. So I need to alias the different versions. In vb.net you can do aliases on an imports statement like:
Imports version5 = Somedll.Something
The problem is I can't setup an assembly reference alias for the different versions of the dll. Apparently in vb.net you can't set these up in the reference properties window. So I tried setting them in in my project file like this:
I want to use project B property in project A. Hence, I added project B to my solution. How can i use the property of B? Can someone guide me? i'm new to vb.net..To my knowledge, we need to use namespace and create a new instance. Could someone guide me on how to use namespace for this purpose?
I'm developing an web application using VB.Net, and I would like to know, if is there any way to make a namespace to be viewed by all project without necessary Imports?
I have an VS2008 solution with 2 projects, WebUI and Domain; WebUI references domain. The Root Namespace in the WebUI project is:MyCompany. MyProjectName.WebUI. The Root Namespace in the Domain project is blank. (Namespaces are manually declared for all classes). So everything has been working fine, until I tried to reference a class in Domain via a fully qualified path: [Code]
Does this make any sense? So, then I cleared my WebUI Root Namespace, and voila, the fully qualified declaration then does work. However, doing this then seemed to invalidate the registration of all my user controls on my pages. The only thing that seemed to solve this was in the codebehind of each user control, manually add a namespace of MyCompany.MyProjectName.WebUI. which might make sense as perhaps the namespaces of the pages somehow had still retained the root namespace value. But, if I was to create a brand new aspx page and drop a user control on (this is before manually adding the namespace), even that page couldn't properly register it. Yet, the user control properly rendered in design view. so the VS UI seemed to be able to properly resolve it, but the compiler seemingly can't.
So from what I can tell, I can at least get things to work by manually wrapping user controls in the proper namespace. Why this is necessary for aspx pages, that have no namespace specified, to see the user controls, seems to make no sense. Is there some fundamental principle I am misunderstanding??
I am trying to create a custom LabelFor helper to apply by default instead of the standard LabelFor helper include in System.Web.Mvc.Html. I want my LabelFor to take model properties that are PascalCase and make a label that appears as multiple words. For example the property FirstName would appear as "First Name".
I found this post that shows how to make a custom LabelFor helper that allows the addition of html attributes. I recreated this helper in VB.Net and modified it to do what I want, but I am not able to get it to work.
[Code]...
The sample includes this Module in Namespace System.Web.Mvc.Html but when I add the namespace declaration to this module everything in the rest of the project goes haywire. For example, each of my models has a Primary Key property that is a Guid datatype and as soon as I add the namespace above to the module, I get several errors stating that System.Guid is not defined among other similar errors.
I've tried to import my project namespace into a view in order to use the custom helper, but then I get an error that says Overload resolution failed because no 'LabelFor' is most specific for these arguments.I am trying to avoid having to specify a DisplayName for every PascalCase property I have in many models.
Is that possible to create a class in vb.net that is not in the default namespace of the project?
for example, say you have a project call sample1, then automatially IDE will have everything default to the Sample1 as your namespace root rather than under global, which is find for most case.but I want to create some classes that is directly under global namespace
I've just picked up a project from someone who has recently left our company, and the project file for the project has somehow had XML documentation deactivated. Typing ''' no longer automatically creates XML documentation segments, and existing XML documentation within the code does not show up in Intellisense, and is also not correctly highlighted as XML documentation.
In addition, the Intellisense for the My. namespace contains only MySettings, Resources and Setting under the "All" tab. Everything else is missing. Attempting to manually write My. namespace code results in compile errors. These are not problems with the IDE; I can start a new project and both Intellisense and My. work fine in these new projects. I can only assume that this is something which has been set on the project itself.
how can I import the System.ServiceProcess namespace into a WPF project in VB.net (not C#)? The ServiceController object is not in the toolbox in VS2008 and can't see to figure it out. Any ideas? If that particular namespace cannot be imported into WPF projects, could somebody suggest another way of controlling windows services from a WPF application? I know this framework is focused more on multimedia apps, but would really like to switch over some of my tools to WPF.
How does one gain programatic access to the information that is entered into the "My Project" properties Application section?I am able to pick up the assembly name from those properties, but I haven't been able to pick these up.Below is the line of code that makes me interested in picking this up programatically. I have found that if the name within the quotes for Sections (GenConfig) doesn't match exactly what is entered in those properties, I will get an application error during run time.How do I reference that property?Is there a better way to pick that value up?
Dim applicationSettingsSection As ClientSettingsSection = config.SectionGroups("applicationSettings").Sections("GenConfig.My.MySettings")
I am working on a solution that does not name namespaces in code files. Instead it uses the root name space of the project (which is the same across all assemblies). Basically there is only one implicit namespace.
Well, I am trying to isolate some code so that I can run FxCop against it. I explicated named the code file with a namespace to do this. This works for FxCop, but it bricks the entire solution.Visual Studio is now asking me to prefix all uses of the implicit namespace with Global. So instead of:
I'm having some problem with VB project in visual studio 2008, when I open or create a new project in VB only code is displayed in the design tab but no GUI and toolbox is greyed out.
I have a project I built in VB 2010 Express Edition. I copied the project's folder to a flash drive, pasted it into the visual studio 2010 projects folder on a different computer, and opened it with VB 2010 Express Edition on that computer. I can view the code, but when I try to open the design view, I get the following error:
Is there a shortcut to get to the designview form in a winforms project in visual studio 2010.F7 will take you to code behind class form and shift + F7 will take you to design mode. Is there a shortcut to filename.designer.cs formWhere you have the control definitions, delegates (for click event etc). defined. I go to the form often if I change the name of click event etc.I have to go through solution explorer and click on the file. Is there a shortcut like F7 that opens the designer.cs file?
I need to read an xml document from a database record into an XDocument object in order for it to be deserialized. So that the deserialization will work, I need to apply a specific namespace to each of the level 1 elements. So XML looks a bit like this:
[Code]...
How do I prevent the blank/empty namespace being added to each child element of the element to which the required namespace has been applied?
When setting up the Ajax Control Toolkit's AutoComplete control, it creates an utoComplete.asmx and a AutoComplete.vb file. The AutoComplete.vb file automatically ends up in the App_Code folder. I was hoping to move all of these styled-classes into a separate namespace, but the compiler simply does not dig it. Is this possible, or must it be within the presentation layer to access the "Web" related namespaces?
I would use the System.Linq.Dynamic. I added the specified Dynamic.vb file, that starts like this:
[Code]...
to my (VB.NET)solution. Now Visual Studio does not recognize anymore in the project files the System.XXX references, proposing me to change them to Global.System.XXX
I've started to use a Vista machine for development. In case it is significant: I'm using MSBee so that I can code in the Visual Studio 2005 IDE while still building against the 1.1 framework.On the Vista machine, when I tried to build a particular vb project, I got this error:
error BC30464: Namespace or type'Compatibility' in the project-level Imports 'Microsoft.VisualBasic.Compatibility' cannot be found.
The same project built fine on my old XP machine. I checked in this folder on my Vista machine:
C:windowsmicrosoft.netFrameworkv1.1.4322
...and sure enough, "Microsoft.VisualBasic.Compatibility.dll" was missing. So was "Microsoft.VisualBasic.Compatibility.Data.dll". Copying them from my XP machine to my Vista machine allowed me to build the project successfully.I'm just a bit puzzled as to why this happened. Why was "Microsoft.VisualBasic.Compatibility.dll" missing? I'm also not very comfortable with my chosen solution - copying the DLL manually. It works, but surely there must be a better way.
This class is located in the namespace Acme.Infrastructure.Interface.A class with the same name EventArgs exists in the System namespace.In another project in my solution I have a class Acme.BusinessModules.MyModule.MyClass.When attempting to use the EventArgs class I have to fully qualify the class name or the compiler thinks I am using the System.EventArgs class.My understanding of namespace resolution was that the compiler would first look for the class in the current namespace, and then its parents. It seems that the compiler checks in System before it checks in sibling namespaces. Is it correct that System is checked before the sibling? Or is this behaviour caused by other issues (Imports order?)?
I have created my webpage in asp.net in 1024*768 resolution, my problem was that when i change my monitor resolution then the controls in my webpage will be displayed in unmanaged manner .
How to arrange items in my webpage which support multiple resolution ...
Whatever the resolution of my monitor the controls in my webpage will display as it is as managed in 1024*768 reolution !
