fxarch Forum Rss Feed

NEW POST: How about a GUI?

eschneider — Mon, 01 Dec 2008 02:12:39 GMT

Would be much easier to use with some kind of GUI...

NEW POST: NullReferenceException

mtrofin — Sat, 09 Aug 2008 18:04:46 GMT

Indeed, you need .NET 3.5 (which I kinda assumed as a default - my fault!)

Skipping that, another reason could be if you indeed had the typo "nscorlib.dll" - it's mscorlib.dll :)

Let me know which it was, or if it still "acts up"

NEW POST: NullReferenceException

sander — Sat, 09 Aug 2008 11:17:05 GMT

The first time I used deps I run into a simulair problem.
I don't know if this is the same problem but I solved my problem by
installing .NET Framework 3.5

NEW POST: NullReferenceException

nativecpp — Fri, 08 Aug 2008 23:27:25 GMT

nativecpp wrote:

mtrofin wrote:
what parameters did you pass to deps?

I basically used the example:

deps d C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\nscrolib.dll C:\
WINDOWS\Microsoft.NET\Framework\v2.0.50727 :System

btw, it happened soon after it displayed # of assemblies as shown below:

Total number of assemblies: 311

NEW POST: NullReferenceException

nativecpp — Fri, 08 Aug 2008 23:17:20 GMT

mtrofin wrote:
what parameters did you pass to deps?

I basically used the example:

deps d C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\nscrolib.dll C:\
WINDOWS\Microsoft.NET\Framework\v2.0.50727 :System

NEW POST: NullReferenceException

mtrofin — Fri, 08 Aug 2008 22:18:44 GMT

what parameters did you pass to deps?

NEW POST: NullReferenceException

nativecpp — Fri, 08 Aug 2008 20:28:48 GMT

I have the latest F# installed and when I ran deps, I got the following exception and would appreciate if someone can give me some idea:

Unhandled Exception: System.NullReferenceException: Object reference not set to
an instance of an object.
at Microsoft.Cci.MetadataHostEnvironment.UnifyAssembly(AssemblyIdentity assem
blyIdentity)
at Microsoft.Cci.MetadataReader.PEFileToObjectModel.FindAssemblyReference(Ass
emblyIdentity assemblyIdentity)
at Microsoft.Cci.MetadataReader.CoreTypes..ctor(PEFileToObjectModel peFileToO
bjectModel)
at Microsoft.Cci.MetadataReader.PEFileToObjectModel.get_CoreTypes()
at Microsoft.Cci.MetadataReader.PEFileToObjectModel.GetTypeDefinitionAtRowWor
ker(UInt32 typeDefRowId)
at Microsoft.Cci.MetadataReader.PEFileToObjectModel.GetTypeDefinitionAtRow(UI
nt32 typeDefRowId)
at Microsoft.Cci.MetadataReader.PEFileToObjectModel.<GetAllTypes>d__30.MoveNe
xt()
at Microsoft.FSharp.Collections.IEnumerator.lengthT,A(T e)
at Microsoft.FSharp.Core.Operators.usingT,U(T ie, FastFunc`2 f)
at Microsoft.FSharp.Collections.IEnumerator.foldT,A,V(FastFunc`2 f, T x, V
e)
at Microsoft.FSharp.Core.Operators.usingT,U(T ie, FastFunc`2 f)
at <StartupCode$deps>.$App._main()

NEW POST: layering

sander — Wed, 06 Aug 2008 16:27:23 GMT

Thanks, using strong named assemblies worked in my test application.
Unfortonatly my real application depends on assemblies I don't have a strong named version of.

If you have the mechanism working without strong name validation please let me know.

NEW POST: layering

mtrofin — Tue, 05 Aug 2008 20:03:59 GMT

Thanks for this! Found the problem. The problem is with the way I decide that two assemblies are the same. The observed behavior happens when assemblies are not signed. I'll work on a mechanism to optionally disable strong name validation, but in the meantime, a simple way to get around is to sign the assemblies.

Let me know if this works!

(no wonder I never stumbled upon this problem - we've been exclusively looking at the framework assemblies, which, of course, are signed! :))

NEW POST: layering

sander — Tue, 05 Aug 2008 10:43:34 GMT

Thanks, the warning at the end of the output is gone but the violations are not reported.
I made some violations on purpose and noticed the output state an unknown because it's not in the diagram but the dll is in the diagram (as stated in my first post)

Console:
unknown: stemacquisitionmodule.dll -> <Assembly not found: StemAcquisitionServiceModule> because <Assembly not found: StemAcquisitionServiceModule> is not in diagram

Can you help me with this?

NEW POST: So, now what?

WillSullivan — Tue, 05 Aug 2008 02:03:49 GMT

That helps. Thanks!

NEW POST: layering

mtrofin — Tue, 05 Aug 2008 01:10:52 GMT

Nope, you're not missing anything. There was a bug in my book keeping of what's been seen vs. what not. Give it a try now, let me know how it works!

NEW POST: layering

sander — Mon, 04 Aug 2008 21:59:16 GMT

The dll is in the path (c:\bin) i specified

I use the following command

layering FrameworkArchitect.xsd C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll c:\bin

in the output an unknown reference to mscorlib.dll from the stemacquisitionservicemodule.dll is indicated which is correct because mscorlib.dll is not in the diagram
this means that the tool can find the dll but at the end of the output the following error is stated
"file stemacquisitionservicemodule.dll present in layering description, but not found in input set"

Am I missing something?

NEW POST: So, now what?

mtrofin — Mon, 04 Aug 2008 18:56:46 GMT

This is a very general question, actually, so I will not be able to address it completely here. I'll try to brush over some scenarios, though - hope this helps:

- use Deps if you want to understand the overall static dependencies in your application. For example, do this in order to assess the effects of versioning an assembly (since that would impact any other assembly taking a dependency on it).

- use Layering if you are interested in (for example) creating SKUs, each SKU providing additional functionality, and your way of doing that is packaging that functionality in assemblies. Then, you want to ensure that there are no unwanted dependencies between such functionality.

- use PotentialCallers as a debugging aid

NEW POST: layering

mtrofin — Mon, 04 Aug 2008 18:38:37 GMT

Hard to tell just from this. Is it possible that stemacquisitionservicemodule.dll is actually not in the path you gave the tool?

NEW POST: layering

sander — Mon, 04 Aug 2008 17:08:08 GMT

layering.exe doensn't work correctly

violations between layers not found and console logs the following:
- file stemacquisitionservicemodule.dll present in layering description, but not found in input set in console.

FrameworkArchitecture:

<?xml version="1.0" encoding="utf-8" ?>
<FrameworkArchitecture xmlns="http://tempuri.org/FrameworkArchitecture.xsd" Name="EZ-Stem" >
<Layer xmlns="" Name="ABL" ID="ABL" Order="1">
<Group ID="Services" Order="0">
<Bin Name="StemAcquisitionServiceModule.dll" />
</Group>
</Layer>
<Layer xmlns="" Name="Presentation" ID="Presentation" Order="0">
<Group xmlns="" ID="Modules" Order="0">
<Bin Name="StemAcquisitionModule.dll" />
</Group>
</Layer>
</FrameworkArchitecture>

What should I do to correct the input set?

NEW POST: So, now what?

WillSullivan — Mon, 04 Aug 2008 16:26:04 GMT

I have an application. Parts of the application I broke off into their own assemblies; these parts have public classes etc that I expect people to use to extend my application.

Now what? How would I use these tools to better my API?