|
I have a kinda hugh client Form Application running and maintaining. It consist of two sub-systems, 1 for marketing and 1 for management.
It started as a Management applicaiton, created in VS08, so all classes etc. thats created for the Management sub-system (that was the first), was inside the Project root.... Later when I added Marketing Subsystem, I created a directory in the Project root, named 'Marketing' and afterwards I created every single Class and stuff related to Marketing in that folder.
But making folder for sub-systems also means that I have to call Class' and objects from each folder, with the foldername in front.
Eg.:
Marketing.Customer newCustomer = new Marketing.Customer();
instead of:
Customer newCustomer = new Customer();
But is it right or wrong to make those folders for each subsystem, to keep an easy overview of your application? Or should I forget everything about folders in the solution?
|
|
|
|
|
You could just add Using <default namespace="">.Marketing to your using statements.
Once you've done that you can just do Customer newCustomer = new Customer();
This way you can have seperate namespaces for Marketing and Management and thus have something of a filter when coding. *Don't punch me for saying 'filter'  *
Or
You can just open the class file and remove the 'Marketing' bit next to the default namespace.
Try creating a class in the root of the project and then dragging it into the marketing folder, it won't have the Marketing bit.
Also:
Folders mean organizing and structuring you app, it's almost never a bad idea.
|
|
|
|
|
Who is this Hugh of whom you speak?
------------------------------------
I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
CCC Link[ ^]
Trolls[ ^]
|
|
|
|
|
You beat me to it... 
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
It's probably a little late in the day for you, but this is precisely the type of task that things such as IoC and DI were made for. BTW -when you refer to Marketing.Customer, that's the namespace and classname; Marketing may be your folder, but .NET has no concept of the physical file structure of your project, and uses the namespace instead.
|
|
|
|
|
IoC? I havn't practically used that pattern yet, but ain't that some kind of Facade/Controller pattern?
But after what I see in replys, I guess that making folder in the solutions for keeping subsystems controlled, is a good idea, and may be the correct use depending on size of application?
And add the using .Marketing or .Management in the classes, sounds like a nice trick instead of editing 10000 lines of code.
|
|
|
|
|
Hi,
I have a Windows application, within this application I'm wanting to copy particular emails from the Inbox to another user created folder. This is an Exchange email account.
I was adviced that I could use the ExchangeServiceBinding.CopyItem method. I have a few questions regarding this:
1. Is this method available to use in both Windows and Web applications?
2. If it's available to use in Windows applications, how would I go about adding the references for ExchangeServiceBinding to my application? I couldn't find the EWS (ExchangeWebServices) or services wsdl.
Thank you,
Mel
|
|
|
|
|
MWRivera wrote: 1. Is this method available to use in both Windows and Web applications?
Yes. It's a web service that you interact with (actually, a set of services).
MWRivera wrote: 2. If it's available to use in Windows applications, how would I go about adding
the references for ExchangeServiceBinding to my application? I couldn't find the
EWS (ExchangeWebServices) or services wsdl
You need to know which version of Exchange you are targetting. There are, IIRC, three versions that it supports, so you will have to pick an appropriate one. If you are using EWS 2010, have a read of this[^].
|
|
|
|
|
Hi Pete,
Thank you for your quick reply.
We are using MS Exchange 2007. Do you have any information on how I could access the EWS for this in my c# code?
Thank you,
Mel
|
|
|
|
|
First of all, you need to create the proxy reference. This[^] article shows you how to do this with Exchange.
In general, the steps in this[^] article should help you.
|
|
|
|
|
Thank you for the additional information.
I read the first link yesterday on how to add a Web reference. I was unable to gain access to the CAS, I'm assuming I have the FQDN incorrect. Our Exchange accounts are hosted by a third party. Is there anyway to find out the CAS from the account settings in Outlook or anywhere else? If not do you think this is information that a third party host would be willing to share with a client?
Thank you,
Mel
|
|
|
|
|
The host should be willing (and able) to provide you with this information.
|
|
|
|
|
Ok, thank you. I've enquired about it so hopefully they will get back to me soon.
Thanks again Pete. I'll keep you updated.
Thanks,
Mel
|
|
|
|
|
Hi,
I deployed some templates which were working fine till the point where I created a new dll in my project.
As soon as I compiled my solution, I got the error below nothing more than that.
Error 1 The type or namespace 'VisualStudio' doesn't exist in the namespace 'Microsoft' ( an assembly is missing ?)
I moved back till the point where it was working but nothing changed. 2 messages looking as above keep pointing on each of my template.
If someone already met this error or if someone has any idea,
By the way I try to fix it by adding some assembled beginning with
Microsoft.VisualStudio.something but nothing does.
Hoping to have a feedback from you guys,
Thx
|
|
|
|
|
Check the references in your project, and also check the source module that produces the error message for references as above. Without seeing some of your code where the error occurs it is difficult to be more specific.
I must get a clever new signature for 2011.
|
|
|
|
|
Thx Richard,
To be more precise, I get 2 errors similar to the one below per template.
Error 1 The type or namespace 'VisualStudio' doesn't exist in the namespace 'Microsoft' ( an assembly is missing ?)
There is 2 errors messages which are pointing on this part.
<#@ template language="C#" debug="false" hostspecific="true"#>
<#@ include file="EF.Utility.CS.ttinclude"#>
<#@ output extension=".cs"#>
<#@ Assembly Name="System.Core, Version=4.0.0.0, Culture=neutral" #>
<#@ Assembly Name="Microsoft.CSharp, Version=4.0.0.0, Culture=neutral" #>
The rest of the errors messages are pointing onother templates but the line pointed are not existing.
I guess it's coming from somewhere else.
I was expecting to fix it with the 2 Assembly lines specifing my version of dotNEt but without success.
References of this DLL:
-envdte
-Microsoft.Build
-Microsoft.CSharp
-System
-System.Core
-System.Data
-System.Data.DataSetExtensions
-System.Data.Entity
-System.Data.Entity.Design
-System.Runtime.Serialization
-System.Security
-System.Xml
-System.Xml.Linq
To refresh, my errors came up when I've added a new dll. Just after that I unloaded it in order to come back in a normal mode.
This errors keep going on.
I still working on,
In the same time, I created a small project with the same content in order to know if it was coming from my code.
And it works, therefore it's not my code.
Weird error....
|
|
|
|
|
Do you need more details?
I think with this it's enough.
I keep seeking without success.
I really need of your help guys,
Thx by advance 
|
|
|
|
|
Sorry, but this looks like an ASP.NET issue, I suggest you try that forum.
I must get a clever new signature for 2011.
|
|
|
|
|
It's not. That's the way that T4 templates look.
|
|
|
|
|
Thanks, something else for me to get to grips with; I think not!
I must get a clever new signature for 2011.
|
|
|
|
|
Actually, they are really powerful, and very useful for mapping out boiler plate code. Colin Eberhart posted an excellent example here[^] on Code Project.
|
|
|
|
|
Thanks, once I get to grips with WPF properly I'll have a closer look.
I must get a clever new signature for 2011.
|
|
|
|
|
Let me correct those downvotes. I'm not sure who thought this part of the thread should be downvoted, but I bet I can compensate for them.
|
|
|
|
|
Thanks again, I returned the compliment. I do wonder at the mentality of some of the people who visit this site.
I must get a clever new signature for 2011.
|
|
|
|
|
Did you get your issue resolved? I think you need to right click on references, click add, click extensions and scroll down to the assembly with the classes you need. Also after you build open the bin directory and make sure that assembly is in the directory.
I assume you are trying to create an app that uses the templates outside of visual studio?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
