Prev: Create and sort on XML File
Next: SQL Job, Impersonation and Process.Start
From: Bob on 8 May 2010 01:52
On Fri, 7 May 2010 08:12:01 -0700 (PDT), Andrew Falanga
<af300wsm(a)gmail.com> wrote:

>So, now that I know the problem it's on to fix it. Unfortunately,
>fixing it won't be as easy as adding a new reference. I tried that
>and VS refused to do so because it made a circular dependency. LoL,
>if it's not one thing, it's another.
>
>Thanks again everyone,
>Andy

I've been following the thread. Nice of you to get back with the
results. Often a circular reference can be solved by using an
interface as a bridge.
From: Jeff Johnson on 8 May 2010 11:53

"Jeff Johnson" <i.get(a)enough.spam> wrote in message
news:OfHl6wg7KHA.5848(a)TK2MSFTNGP06.phx.gbl...

>> Technically speaking, you can have a multi-file assembly (several
>> files make up a single assembly) but I don't think VS can do it.
>
>> http://msdn.microsoft.com/en-us/library/226t7yxe.aspx
>
>> I'm not sure if there is any benefit to a multifile assembly.
>
> I didn't read the article, but if it's what I think it is I believe the
> main reason for it was to be able to merge the output of multiple
> languages into a single assembly. And no, Visual Studio can't do it; you
> have to use command-line tools.

Also, the ultimate output of the assembly linker is a SINGLE file, unless I
read incorrectly, so when it come to the final output, an assembly is still
one and only one file. I believe that's pretty much part of the .NET
definition of "assembly."


From: Arne Vajhøj on 12 May 2010 16:18
On 07-05-2010 12:41, Chris Dunaway wrote:
> On May 7, 8:35 am, "Jeff Johnson"<i....(a)enough.spam> wrote:
>> "Peter K"<pe...(a)parcelvej.dk> wrote in message
>> news:OcTU3jZ7KHA.420(a)TK2MSFTNGP02.phx.gbl...
>>>>>> I don't understand why, but I cannot see SingletonClass in file 2,
>>>>>> even though SingletonClass is typed as public AND they're both in the
>>>>>> same namespace AND part of the same solution. What's further odd, the
>>>>>> SingletonClass doesn't show up in .NET reflector. What gives? What
>>>>>> subtle aspect of access modifiers am I missing?
>>
>>>>> Are they part of the same assembly?
>>
>>>> They are in the same assembly and in the same solution, though they
>>>> are in different projects (i.e. DLLs then). I'm terribly sorry about
>>>> the typos. The code, as it exists now, compiles and has been working
>>>> for quite some time. I need to make some additions for new support.
>>
>>> Do you references between the projects?
>>
>>> And I have an additional question: can you have separate projects that
>>> compile to the same assembly?
>>
>> No, you can't, which is where Andrew is confused. If they are part of
>> different DLLs then they are in different assemblies. There is only one
>> NAMESPACE, but there are multiple ASSEMBLIES. Remembers, an assembly is
>> ultimately a file, whether it be an EXE or a DLL. This is why I asked the
>> question in the first place, and I think the whole issue might simply be one
>> of needing project references between the two, like you suggested.
>
> Technically speaking, you can have a multi-file assembly (several
> files make up a single assembly) but I don't think VS can do it.
>
> http://msdn.microsoft.com/en-us/library/226t7yxe.aspx
>
> I'm not sure if there is any benefit to a multifile assembly.

Those "multifile assemblies" are still just one DLL - they
are just called multifile because they contain multiple modules.

Arne
From: Arne Vajhøj on 12 May 2010 16:19
On 07-05-2010 13:39, Jeff Johnson wrote:
> "Chris Dunaway"<dunawayc(a)gmail.com> wrote in message
> news:78a826db-98dc-4ac0-bc86-03f55dfa2acb(a)n15g2000yqf.googlegroups.com...
>> Technically speaking, you can have a multi-file assembly (several
>> files make up a single assembly) but I don't think VS can do it.
>
>> http://msdn.microsoft.com/en-us/library/226t7yxe.aspx
>
>> I'm not sure if there is any benefit to a multifile assembly.
>
> I didn't read the article, but if it's what I think it is I believe the main
> reason for it was to be able to merge the output of multiple languages into
> a single assembly.

Yes.

> And no, Visual Studio can't do it; you have to use
> command-line tools.

But command line tools are an option. And an option used for
many large projects.

Arne

From: Arne Vajhøj on 12 May 2010 16:22
On 07-05-2010 09:46, Andrew Falanga wrote:
> I completely understand, and appreciate, the struggle to help without
> the actual code. I cannot post that here due to company
> restrictions. Also, you wouldn't want to wade through it since it's
> several thousand lines.
>
> Unfortunately, I cannot post a working example, much beyond the
> skeleton code already posted, because to do so would require that I
> understood the problem. I do not.

You can almost always create an SSCCE.

Take the real code.

Delete all classes/methods/properties/fields not
necessary to reproduce the problem.

Delete everything in method bodies not necessary
to reproduce the problem.

Rename all names to neutral names.

Post it with build instructions and the error
you get.

Arne
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Create and sort on XML File
Next: SQL Job, Impersonation and Process.Start