|
How do I know an assembly was created under which version of .net framework ?
|
|
|
|
|
Run ILDasm > Open the assembly > double click the manifest node
The first line shows the .net version it was compiled.
// Metadata version: v1.1.4322
Thanks
Laddie
Kindly rate if the answer was helpful
|
|
|
|
|
Thanks. But I can't find such information here, Is there anything am I missing?
|
|
|
|
|
You mean to say you are not able to find the ILDASM tool or you are not able to find the manifest node ?
Thanks
Laddie
Kindly rate if the answer was helpful
|
|
|
|
|
When I use ildasm to open assembly, there is no such information you provided in manifest node.
|
|
|
|
|
You should double click the manifest node to open in a text viewer to see it
optionally you can go to the view menu > header
In the text find out the section called clr header it will be someting like this
----- CLR Header:
Header size: 0x00000048
Major runtime version: 0x0002
Minor runtime version: 0x0005
Which will give you the major and minor version of runtime required.
Thanks
Laddie
Kindly rate if the answer was helpful
|
|
|
|
|
I get what you said when I using ildasm v2.0, previously, I use ildasm1.1.
Thanks.
|
|
|
|
|
In a large organization, if you have UNIX applications, mainframe applications, Windows applications, etc. How do you get these to talk to each other?
may i know how .NET solve this problem ?
also, during deployment,we have to worry about which version of IE is installed, which version of MDAC is installed, etc. we may have to test our install on Windows 95, 98, ME, NT, 2000, and XP, with different service packs, to insure that the install and uninstall work correctly.
may i know how .NET solve this ?
|
|
|
|
|
|
Find out more about Mono, an open source Linux .NET Runtime and Framework.
Semicolons: The number one seller of ostomy bags world wide. - dan neely
|
|
|
|
|
Hi, i am taking a look into the windows updates and I have found a service pack 2 for .Net Compact Framework. I have already installed the .Net Framework 2.0 and 3.0 with both Service Packs 1. Should I get this update? Are there differences between them? (If yes... which)
Thanks.
Greetings.
--------
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
modified on Wednesday, May 21, 2008 1:15 PM
|
|
|
|
|
Nelek wrote: Should I get this update?
No. Never install updates, 3 out of 4 Security Experts agree updates can cause cavities.
led mike
|
|
|
|
|
Damn, I was hoping this would be a bit like the SUBJECT of the title, not even what OP SAID,
Can someone seriously though explain the differences in .NET CF and just .NET Framework, is it just that simple? I just don't get it, I am new to the mobile programming, and this has seriously recently fugged with me, my program requires .NET CF 2.0, on the pda .NET FRAMWORK 2.0 (blah blah long number) is loaded, however I CAN successfuly install .NET CF 2.0 on my windows mobile 5 pda. It then shows in Add / Remove Programs - however my Windows Mobile 6.0 PDA (even changed the platform so it would be a 6.0 app) No .NET CF shows up in the add / remove / programs - try to install NET CF 2.0 it says, there is a newer version already on it and to uninstall it - but like I said it doesnt show it in the add and remove, so I check the .NET FRAMWORK version of the PDA and its the same as the other one, however my app wont run on it, because I cant install the CF 2.0.
Sorry if I ranted a bit, but I'd really love to get schooled on what the differences is in the two? Is CF just simply compact meaning its for a mobile/compact device? Gosh, makes me want to go back web programming.
Computer Programmer Web/Mobile .NET
|
|
|
|
|
Compact Framework is, yes, just for mobile device programming on Windows CE and Windows Mobile. There's a different version for different devices.
Further complicating matters is that Windows Mobile 2003 and newer have versions of .NET Compact Framework in ROM. This ROM version is used if no version is installed to the filesystem. The ROM version, however, has been universally either the wrong version or buggy. .NET Compact Framework 1.0 was useless before SP2 and you should use SP3 if you plan to use this version, but I would recommend universally upgrading to Compact Framework 2.0 as there were numerous problems with CF 1.0 (not least very poor performance). Windows Mobile 5.0 generally came with CF 1.0 SP2 in ROM but the OEM could override this and I think some of Microsoft's OEM Adaptation Kit Updates (AKUs) included a newer version.
I haven't yet handled a Windows Mobile 6.0 device but it would be reasonable to expect that these come with Compact Framework 2.0 in ROM. Yours may well have the same version that you're trying to install.
To show the latest version(s) of Compact Framework installed on the device, navigate to \Windows in File Explorer and run the cgacutil program. This will show one line for each major release present (i.e. one for 1.0, one for 2.0, one for 3.5) indicating the build number. See here[^] for the list of build numbers versus service pack number.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
.NET Compact Framework is for mobile device programming (Windows CE and Windows Mobile). If you don't do any mobile device programming, don't worry about it.
If you do, this update will update the version of .NET Compact Framework that Visual Studio automatically deploys to the device when you start a debug session. The service packs fix a number of serious issues like leaking memory when doing P/Invokes.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
Thanks for the info.
Greetings.
--------
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
|
|
|
|
|
Hi,
I am working on an application that is able to read data from a keyboard wedged barcode scanner.
I want the barcode that is scanned to be displayed in a picture box in my form.
I use the code discribed in http://www.codeproject.com/KB/macros/BarcodeLibrary.aspx
to draw the barcode. Therefore I need 2 things :
1) the data to be encoded.
2) the type of the encoding (Code39, Code128, UPC A, UPC E, EAN13 etc..)
Since most barcode scanners are able to read several barcode types, is it possible to determine the type of the encoding the barcode reader uses to generate the data from a barcode image?
TIA
|
|
|
|
|
|
Barcode scanner hardware is generally able to read any barcode of a particular layout. 'One-dimensional' readers such as wands (which look like a pen you 'draw' along the length of the symbol) and lasers can generally read any one-dimensional code, that is, where the symbol consists of a sequence of parallel lines of varying thicknesses and spacing, and some can read two-dimensional codes which consist of a stack of one-dimensional codes, such as PDF or DataMatrix. The new Reduced Space Symbology, recently renamed DataBar, may be too new for some scanners - they may need a firmware upgrade.
Imagers, which simply take an image in the same way as a digital camera, can generally handle both 1D and 2D barcodes. They struggle if the barcode is very long, though, as the scanner needs to be placed a long way from the code to fit it all in to the image, and then the resolution of each line is not very good, making measurement of the bars and spaces difficult. Most methods of encoding - referred to as symbologies - are self-checking, meaning that the scanner just won't return anything, rather than returning incorrect data.
The different symbologies are designed for different purposes. For example, UPC and EAN are for encoding Global Trade Item Numbers, basically Stock Keeping Unit codes which identify a product in retail. That's their sole purpose and they shouldn't be used for anything else. If you're marking a product for sale by high-street retailers, you need a GTIN for your product, which means you need to register with your local GS1 Member Organization[^] to get a Company Prefix, a range of item numbers assigned to you. If you're in the US, this will be a UPC; if abroad, an EAN. In fact the two symbologies are the same thing, except that EAN changes the parity of some of the bars in the left-hand half of the code to encode the first digit. The original UPC parity scheme represents a '0' in EAN, the country code for the US in the GS1 system.
If your item is a book, it should have an ISBN (International Standard Book Number) and the barcode should be derived from that. A book barcode is an EAN, and traditionally started 978, then the first 9 digits of the ISBN (the tenth was a check character), then the EAN check digit. Because the 10-digit ISBN is close to being exhausted, new books are getting an 'ISBN-13' which is simply a GTIN; in future a new prefix will be issued if it hasn't been already. Magazines, newspapers and other periodicals start 977. Some books may have a 'supplemental' of five digits indicating the price or price code. Magazines often have a 2-digit supplemental indicating the issue number, so the base GTIN stays the same between issues and only the issue number is varied.
UPC E is simply a scheme for suppressing consecutive 0s in some UPC A barcodes to provide a shorter code. A UPC E code can (and in my view, should) be converted to the canonical GTIN representation when being read.
Retail products can also be marked with an EAN 8 barcode, which is a different number from the EAN 13 code. Some sources say that the EAN 8 code is a derivation but I believe this is incorrect.
For shipping containers of retail products, you should generally mark with Interleaved 2 of 5 (ITF) or GS1-128 (formerly called EAN-128). The former encodes two characters at a time, one with the lines, the other with the spaces (hence interleaved). Because of this it can only encode an even number of digits. ITF has a bug: the start and stop characters are underspecified, and some codes can be interpreted incorrectly if the scanner beam exits the top or bottom of the code (e.g. scanned obliquely). To prevent this, ITF is commonly used with thick black horizontal bars touching the top and bottom of the data bars.
GS1-128 is simply a Code 128 barcode with specific encoding rules to enable it to carry more than one piece of information. Those rules dictate the way that different pieces of data are encoded and delimited so that software can extract each piece of information. Couriers often use a subset of GS1-128 they call a 'license plate' for each package.
The airline industry I believe uses a special variant of ITF called IATA-2 of 5 which has different start and stop characters to avoid the partial decode problem.
Other symbologies are pretty generic and have certain properties which lend themselves to different purposes. As mentioned, Interleaved 2 of 5 can only encode numeric data but its length is bounded only by the practical limit of how wide the barcode can be. Code 39 encodes upper case Latin characters in addition to the numbers, plus a few symbol characters as well. There is also a standard extension to Code 39 called Full ASCII, where other characters from the ASCII set are encoded by escaping using the symbol characters; however, it is not possible to detect whether a barcode is intended to be Full ASCII or not. A variant of Code 39, Trioptic 39, uses different start and stop characters.
Code 39 has a small advantage in one way in that each character is encoded as a pattern starting and ending in a bar - the space between characters is not significant. This allows 'bar code fonts' to be used with word processors which might adjust this spacing, as long as the modules themselves are not distorted. Other symbologies such as Code 128 are continuous, that is they start with a bar and end with a space of a designated width.
Code 128 can encode the full ASCII character set. It does this not by having 128 distinct patterns but by having 'code sets' where the 103 different patterns have different meanings depending on which code set you're in. There are patterns reserved for shifting code sets, and three different start characters to indicate the code set used at the beginning. For a fully numeric barcode, Code 128 can be more compact by using Code Set C, where 100 of the patterns represent two digits, 00 to 99. (The remaining three are 'shift to Code A', 'shift to Code B', and 'FNC 1', a generic non-printable character that is used to indicate a GS1-128 code and delimit variable-length elements of a GS1-128 barcode).
Generally, if you're just encoding something for your own purposes I'd use Code 128, unless you want to take advantage of barcode fonts in which case Code 39 might be more appropriate.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
 OK - this has to be your most comprehensive answer to date.
|
|
|
|
|
Well, when you've worked with barcodes for seven years, you pick a few things up!
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
That's fair enough, but for somebody who's renowned for giving comprehensive answers you've outdone yourself this time.
|
|
|
|
|
Mike Dimmick wrote: Imagers, which simply take an image in the same way as a digital camera, can generally handle both 1D and 2D barcodes.
FYI, there's a third category of reader (probably not used so much anymore, now that imagers have become cheaper): raster-scanning lasers can scan 1D barcodes and PDF-417 but not other 2D symbologies. PDF-417 is designed so that it can be read by combining many independent one-dimensional reads. If a particular read crosses from one 'row' to the next, the character on which the crossing occurred will not be read, but the system will detect the crossing and can thus properly assign the following characters to the appropriate row.
I mention this for a few reasons:
-1- I think PDF-417 is a really cool technology which, although it's obsolete, still deserves to be appreciated and marveled at.
-2- While I don't know the market situation, I would not be surprised if used raster-scanning lasers are or will be available cheaper than other imaging technologies. If information capacity is more important than small symbol size, using PDF-417 may allow one to equip one's shop with compatible readers more cheaply than other symbologies.
-3- With a firmware upgrade, a line scanner that has enough memory should be able to handle PDF-417 barcodes if the user waves the scanner slowly over the barcode a few times, though I'm not aware of any that do. This might make an interesting hobby project, though.
-4- PDF-417 barcodes are physically larger than other 2D barcodes with similar information content; it may be nice to understand why.
|
|
|
|
|
Some scanners that connect via serial port or PS/2 keyboard port can be configured so as to prefix each data record with a character indicating the encoding. This will likely cause problems with any application that doesn't expect such a thing.
I would expect/hope that USB-based readers could be configured so that an application that was interested in the encoding on a barcode could ask, while those that weren't interested wouldn't be bothered with the information. Actually, what would be ideal would be if a USB-based reader had a driver that could be configured to behave differently based upon what application was open, but I haven't looked into whether such things were possible.
|
|
|
|
|
Hi all,
I have a .net framework v3.5 that requires XP service pack 2. Have problems downloading the service pack. Any help
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
