This project is read-only.

can you help me?

May 8, 2012 at 3:31 PM

i download the last version project file .i want user it on my website .but the  code can't go as usual ,i use the renderer which used can be user .this time can't work .so i user the last version's


GraphicsRenderer renderer = new GraphicsRenderer(2);

 but it can't work .it said the param is wrong ,and could'nt work.

May 9, 2012 at 12:47 AM

First, param is wrong. I have redesigned all renderer. If you want to check full documentation I will post link below.


Second, as you want to use it on your website, are you using it with ASP.Net or Silverlight. As GraphicsRenderer is for Winform's Graphics class, which is under namespace System.Drawing. 

For silverlight, I haven't put it into main stream, but it is available under one of issue thread.

Download - SilverlightQR Geometry Control and Image control.7z

Newest implementation will not simply ask you to input module size. It has two option, FixedCodeSize or FixedModuleSize. 

CodeSize = QrCode's pixel width. 

ModuleSize = QrCode each small module's width. 

So now format is like this. 



GraphicsRenderer renderer = new GraphicsRenderer(

        new FixedCodeSize(200, QuietZoneModules.Two))



If you have further question just leave behind. 

For Silverlight I will sort it out and put it in before next release. The one I post there should work mostly fine. 

May 9, 2012 at 3:24 AM
Edited May 9, 2012 at 3:25 AM

Thanks very much,

with you help i solve it ,

and i user it on web site ;it work well.

   public void CreateImage(string sampleText)
        QrEncoder qrEncoder = new QrEncoder(ErrorCorrectionLevel.H);
        QrCode qrCode = new QrCode();
        qrEncoder.TryEncode(sampleText, out qrCode);
        const int moduleSizeInPixels = 5;
        GraphicsRenderer renderer = new GraphicsRenderer(new FixedModuleSize(moduleSizeInPixels, QuietZoneModules.Two), Brushes.Black, Brushes.White);
        MemoryStream ms = new MemoryStream();
        renderer.WriteToStream(qrCode.Matrix, ImageFormat.Png,ms);
        Response.ContentType = "image/Png";


Aug 3, 2012 at 5:51 PM


ElmerWang how did you manage to use the control in the asp proyect ?

I for the life of me, can't event reference the dll to the proyect it displays a warning on the reference list in the solution explorer and i don't see the methods ( obviously ) when i type "QrEncoder qrEncoder = new QrEncoder(ErrorCorrectionLevel.H);"

It's been 2 days and i'm starting to think that the dll that i downloaded is just for winforms.

If anyone reads this, could you help me solve this please?


-- Sam.

Aug 3, 2012 at 10:08 PM

What's that exception you talking about? Also your project's .Net version. The dll from this website is .Net 4.0. If you are working on .Net 3.5, you have to download source code and compile yourselves. 

Aug 3, 2012 at 10:27 PM

Hello and thank you for your feedback.

My project is indeed 4.0, I created a new project just to test the dll and in this project i can get it to work, maybe there's something wrong with the project i'm working on.

This is a legacy project that spawned in the early .Net Framework 1, then started from scratch ( supposedly ) for Framework 2 and then ported to 3.5 and currently it's being rewritten ( mostly ) for 4.0 maybe some (legacy) dependencies are interfering with the control?

The exception is not really an exception is just the warning icon that shows in the reference list that tells me that something's wrong about that reference, i can't get it to live with the rest of the project.

Anyway, I'll try to figure this one out and come here with the outcome.

The control that we are currently using is MessagingToolkit's QRCode, It's fast and easy to setup, but this project seems best in my opinion.

Thanks again and see you later.


Aug 4, 2012 at 12:27 AM

Sounds weird. Our library doesn't use any dependency library, it's purely written in native official C# framework. 

Download source code from our project page and check which library we have been using and compare to your project. 

Another thing is that our assembly is not signed. It will be in next release version. Not sure if that can be problem.