|
|
|
|
|
Total Hits: 42 | Today: 0
|
Author: Mark Killmer
|
Rating:
|
|
When working in a team environment, factors such as limited license keys, security, or network access may hinder the creation of a test environment. In a recent project, one of my requirements was to interface with an existing .NET component. The existing component could not be duplicated in my off-site office environment, and existing security policies would not allow network access. Coding and testing the interface was looking very difficult....
|
|
|
|
Total Hits: 42 | Today: 0
|
Author: Daniel Ch. Bloch (MCSD, MCAD, MCTS)
|
Rating:
|
|
There are some very nice areas in the CLR, for example the whole area of reflection. Nowadays, developers use reflection, its functionalities for their projects. But it's nearly impossible to know all about these functions.
So I made some test just on the Assembly.LoadFrom and played around with it......
|
|
|
|
Total Hits: 35 | Today: 0
|
Author: r@hu!.
|
Rating:
|
|
I faced this issue today. I wanted to call a function written in C# from my VB.NET code, but I found out that the coder of the library had not followed Microsoft guidelines for interoperability and had used same name for two functions differing only by case having the same signature. I didn't have access to the C# code, so was helpless as VB.NET does not allow me to use any of these functions....
|
|
|
|
Total Hits: 211 | Today: 0
|
Author: Mike Gunderloy
|
Rating:
|
|
Microsoft .NET provides several ways to think of your code as more than just a bunch of disconnected lines. As a Visual Basic programmer, you're already familiar with the concept of a class, a section of code that defines an object and its behavior. But two of the higher-level groupings may be unfamiliar to you:
1.An assembly provides a fundamental unit of physical code grouping. 2.A namespace provides a fundamental unit of logical code grouping.
As you'll see in this document, you can u...
|
|
|
|
Total Hits: 39 | Today: 0
|
Author: Alan Dean
|
Rating:
|
|
I have been developing shrinkwrapped software products for most of my professional career. Therefore, I have an abiding respect for internationalization and localization. In fact, it is something of a running joke to warn new developers who join not to kick me off on the subject. Of course, they will hear from me soon enough....
Shrinkwrapped products can end up in a bewildering set of environments and countries. Simply saying that your product will only run on {insert OS} with {insert la...
|
|
|
|
Total Hits: 152 | Today: 0
|
Author: Bill Hatfield
|
Rating:
|
|
Deployment issues often get swept aside when deadlines overtake you and getting it out the door is all that matters. But, if maintaining the code is also a consideration, you'd do well to take note of the following assembly deployment best practices....
|
|
|
|
Total Hits: 171 | Today: 0
|
Author: Nayan Patel
|
Rating:
|
|
An assembly is the primary building block of a .NET Framework application. It is a collection of functionality that is built, versioned, and deployed as a single implementation unit (as one or more files). All managed types and resources are marked either as accessible only within their implementation unit or as accessible by code outside that unit. There really isn’t VB6 equivalent of an assembly but VB6 exe/dll comes closer to the concept of Assembly but again Assembly can be made of multiple ...
|
|
|
|
Total Hits: 172 | Today: 0
|
Author: Ted Pattison
|
Rating:
|
|
This month's installment of Basic Instincts will begin a multi-part series focused on working with assemblies. There is quite a bit you need to know about how assemblies are built, deployed, and versioned. This month I will address several essential details about how to build an assembly with the exact name you want. In subsequent months, I'll discuss your options for deploying assemblies on a production machine and revising assemblies that have already been put into production....
|
|
|
|
Total Hits: 265 | Today: 0
|
Author: Sheakar Krishna
|
Rating:
|
|
This article discusses how to build assemblies and secure them from being tampered. This article will brief you from the basics of the assembly till the signing of the assembly and preventing it from tampering....
|
|
|
|
Total Hits: 290 | Today: 0
|
Author: Mihir Pathak
|
Rating:
|
|
This article allows you to read the assembly attributes information using .NET. The information store in AssemblyInfo files like Title, Description, copyright, Trade mark can be read using reflection and assembly namespace....
|
|
|
|
Total Hits: 3 | Today: 0
|
Author: authors.aspalliance
|
Rating:
|
|
Today's topic will be discussing again the assemblies, but this time I will be giving you an idea of how multiple or (in other words what might be also called as) sub namespace assemblies are implemented. The .NET framework consists of many assemblies. In our ASP .NET projects we also use many different type of assemblies, depending upon the projects or the solutions requirements. Some of the assemblies have Namespaces which differ at a certain level, for example; you would have included the Sys...
|
|
|
|
Total Hits: 27 | Today: 0
|
Author: rj45.
|
Rating:
|
|
First off, get the assembly from type integer. This should get the mscorlib.dll. (Main .NET assembly)....
|
|
|
|
Total Hits: 29 | Today: 0
|
Author: Fons Sonnemans
|
Rating:
|
|
During development, you can use the output methods of the Debug class to display messages in the Output window of the Visual Studio integrated development environment (IDE)....
|
|
|
|
Total Hits: 240 | Today: 0
|
Author: Sheldon Fernandez and Alim Somani
|
Rating:
|
|
Assemblies are the new way components and executables are packaged in the .NET Framework. The EXEs and DLLs created by VB.NET are assemblies. Assemblies contain both IL code and metadata. Metadata describes the types an assembly exposes, the assembly's dependencies, and the assembly's versioning information. The CLR uses an assembly's metadata to ensure that its methods are called in a type-safe manner and that an assembly runs against its proper resources....
|
|
|
|
Total Hits: 252 | Today: 0
|
Author: Shekar Krishna
|
Rating:
|
|
This article discusses how to build assemblies and secure them from being tampered with. Every assembly built using the .NET compiler has a four-part name consisting of the elements, Friendly name, Version number, Culture setting, Public key or public key token. The first part is a friendly name Like MyAssembly. The second part is the version number say 1.0.5.0. These four numbers represent the major version, minor version, build number, and revision number respectively....
|
|
|
|
|
|
