Web Developer Recruitment in Faraconesh Corporation

Faraconesh Logo

I hardly ever use my blog to publish unrelated subjects to programming. This is one of them.

Our company Faraconesh Corporation is bound to hire new talented and professional .NET developers. If you like working with me in person in a small-growing company which offer good salary, insurance, flexitime working beside experts which are pioneers in Iran in their skills and you meet the following needs

At least 3 years of relevant experiences.

Deep knowledge of .NET, C#, SQL Server and NHibernate

Also ability to work in team and using issue trackers, source controls and the rest of teamwork tools

Ability to work with WPF, WCF, WF and REST count as advantages

You can send your resume to jobs@faraconesh.com or to me at n.hajloo@gmail.com.

Faraconesh Corporation appreciates in advance your kind request to join and will arrange a meeting with you in next few days.

This is the Persian text for this advertisement.

کروکی آدرس شرکت فراکنش در نقشه تهران کتاب اول
من به ندرت در این وبلاگ مطالب غیرمرتبط با برنامه نویسی می‌نویسم. این مطلب یکی از آنهاست.شرکت ما، فراکنش قصد استخدام چند برنامه‌نویس بااستعداد و حرفه‌ای دات نت را دارد. اگر شما دوست دارید که با من از نزدیک در یک شرکت کوچک رو به رشد که حقوق کافی، بیمه، زمان کار آزاد و کار شانه به شانه با متخصصینی که در زمینه کاری خودشان از پیشروان هستند همکاری کنید و نیز درصورتی که شرایط زیر را دارید

حداقل سه سال سابقه کار مرتبط

درک و تسلط کافی و عمیق از ‫.NET, C#, SQL Server و  NHibernate

همچنین توانایی کار گروهی و استفاده از ابزارهای کار تیمی مانند ایشوترکر ها و سورس کنترها

توانایی کار با WPF, WCF, WF و REST مزیت به شمار می‌آید

را دارید

می‌توانید رزومه کاری خودتان را به آدرس jobs@faraconesh.com و یا برای من به آدرس n.hajloo@gmail.com ارسال نمایید.

شرکت فراکنش از درخواست همکاری محبت آمیز شما از قبل قدردانی کرده و در چند روز آینده یک قرار ملاقات با شما تنظیم خواهد کرد

Microsoft SQL Server 2008 Service Pack 2 Released

SQL Server 2008

Microsoft SQL Server 2008 Service Pack 2 (SP2) is now available for download. These packages may be used to upgrade any edition of SQL Server 2008. Service Pack 2 contains updates for

  • SQL Server Utility,
  • Data-Tier Application (DAC),
  • as well as integration capability for Microsoft Reporting Services with the Microsoft SharePoint 2010 Technologies.
  • Service Pack 2 introduces support for a maximum of 15,000
  • artitions in a database,
  • and includes SQL Server 2008 SP1 Cumulative Update 1 to 8.

While keeping product changes contained, we have made significant investments to ease deployment and management of Service Packs.

Note: Microsoft SQL Server 2008 Service Pack 1 is not a prerequisite for installing SQL Server 2008 Service Pack 2.
You Can check the Release Notes here.

SQL Server 2008 Management Studio Splash Screen

New Features of SQL Server 2008 SP2

  1.    15K partitioning Improvement. Introduced support for a maximum of 15,000 partitions in tables and indexes in Microsoft SQL Server 2008 Service Pack 2 in the Enterprise, Developer and Evaluation Editions. For details on how this support can be enabled and disabled, along with recommended operation paramaters, see the white paper Support for 15000 Partitions.
  2.    Reporting Services in SharePoint Integrated Mode. SQL Server 2008 SP2 provides updates for Reporting Services integration with SharePoint products. SQL Server 2008 SP2 report servers can integrate with SharePoint 2010 products. SQL Server 2008 SP2 also provides a new add-in to support the integration of SQL Server 2008 R2 report servers with SharePoint 2007 products. For more information see the “What’s New in SharePoint Integration and SQL Server 2008 Service Pack 2 (SP2)” section in What’s New (Reporting Services).
  3.    SQL Server 2008 R2 Application and Multi-Server Management Compatibility with SQL Server 2008.
      •   SQL Server 2008 Instance Management.With SP2 applied, an instance of the SQL Server 2008 Database Engine can be enrolled with a SQL Server 2008 R2 Utility Control Point as a managed instance of SQL Server. For more information, see Overview of SQL Server Utility in SQL Server 2008 R2 Books Online.
      •   Data-tier Application (DAC) Support. Instances of the SQL Server 2008 Database Engine support all DAC operations delivered in SQL Server 2008 R2 after SP2 has been applied. You can deploy, upgrade, register, extract, and delete DACs. SP2 does not upgrade the SQL Server 2008 client tools to support DACs. You must use the SQL Server 2008 R2 client tools, such as SQL Server Management Studio, to perform DAC operations. A data-tier application is an entity that contains all of the database objects and instance objects used by an application. A DAC provides a single unit for authoring, deploying, and managing the data-tier objects. For more information, see Designing and Implementing Data-tier Applications.

Downloads

Download Microsoft SQL Server 2008 Service Pack 2

Download Microsoft SQL Server 2008 SP2 Upgrade Advisor

Download Microsoft SQL Server 2008 Service Pack 2 Feature Pack

Download Microsoft SQL Server 2008 SP2 Express Edition Service Pack 2

Download Microsoft SQL Server 2008 SP2 Reporting Services Report Builder

Download Microsoft SQL Server 2008 SP2 Reporting Services Add-in for Microsoft SharePoint

News Copied from Bink.nu. News Reference Link

What is Reporting Services and How to create a server-side Report

SQL Server 2008

As you all know nowadays reporting is one of the important sections of each application, specially official and financial ones. So that there are lots of reporting services which provide some feature for developers to create custom reports. Most of you are aware of some reporting services in each programming language like Crystal Report, Jasper Report and etc. most of these reports create xml document from your custom reports and show it to users with a report viewer which compile the xml and show the result.

In order to creating powerful and robust reports, since 2005 SQL Server provides a Reporting Service which formerly named SSRS or SQL Server Reporting Services. So to use SSRS you have to buy a Developer or Enterprise edition. After installation you’ll have a ‘SQL Server Business Intelligence Development Studio’ which allows you create Server-side reports.

SSRS 2005 used schema 2005 and SSRS 2008 using schema 2008 for creating server-side reports. I wrote many posts about SSRS before so if you are a fan of this blog, you’re aware of these schemas and differences. Visual Studio has a built-in reporting system which allows you to create client-reports (RDLC) and it use schema 2005 to do its job.

When we use SSRS instead of VS Reports

Client reports which provided by VS are suitable for available data. For example you have a list of users or asset and you want to get a report from it.

Server reports which provided by SQL Server, use for reports which need calculation and in some cases take some minutes to generate, cause data have to generate based on some parameters.

SSRS (schema) 2005 has lots of issues with RTL and Unicode but SSRS 2008 resolve most of them and there are only a few problems that can be neglected.

Upgrading reports from schema 2005 to schema 2008 is a real nightmare that I wrote about it and its solution, but you have to know that it’s not an easy job.

How to create a server side report in SSRS 2008

  • Open Visual Studio
  • Create a new project and choose Business Intelligent Projects from the left pane and then select Report Server Project
  • Give a Name to your project
Creating a Reporting Services Report Project
Creating a Reporting Services Report Project

Your server-side project is ready, now you have toad a new server reports to it to do this

Add a new Item and select Report (note to format of the report, it is RDL)

Now you have an empty report and you can design it with Toolbox items and bind it to your database with Store procedure or via a simple query

Downgrading Report schema version and Report Viewer Nightmare

Nightmare
Nightmare

In most cases upgrading applications is a good idea, but in this week we have to downgrade our Reports to an older version. The scenario is that We had some SSRS 2005 reports in the past and we upgrade those to SSRS 2008 reports, so we actually upgrade our Report definition schema from 2005 to 2008 which I wrote an article about it at the past. Currently we decide to convert our SSRS server reports to Visual Studio Client Reports which has some benefit for us, but unfortunately Visual Studio 2008 use Older version of report schema and the nightmare begun here.

—————————————————————-

GNU Logo
GNU Logo

‪Title : Downgrading Report schema version and Report Viewer Nightmare

‪Publish Date : 09/05/2010

‪Version : 1.0

‪Author : Nasser Hadjloo

‪Author Mail : n.hajloo@gmail.com

‪Copyright (c) 2010 Nasser Hadjloo.

‪Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

‪with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

SQL Server Reporting Services (all editions) and Visual Studio Reporting use ReportViewer control to display Reports, but it’s not the end, it’s just the beginning of a nightmare.

SSRS 2005 and Visual Studio 2008 & 2005 using 2005 Schema to create reports which is an older version of schema so that it missed some newer items which it’s obvious.

SSRS 2008 RDL reports use 2008 schema to create reports (in this schema we have some new features to create reports like Tablix or etc)

Visual Studio 2010 using Schema 2008 to create RDLC reports.

Report Viewer 2005 (& RV SP1) only understands 2005 schema and older versions.

Report Viewer 2008 understands 2005 schema and older versions. And there is no noticeable option which included in this version.

Report Viewer 2008 Service Pack 1, resolved some issues (installation and etc) and also apply some patches for some performance issues.

Report Viewer 2010, has a few limitation (won’t install in XP SP2 – only XP SP3 accept installation) but resolved all issues and works fine with Schema 2008. This version work very well with Asp.net Ajax and Ajax functionality like AsynchPostback and etc.

With these background, just imagine you have a SSRS 2008 report which implemented by schema 2008, and you want to convert it to VS 2008 Client Report which use older schema (2005). Following options may help to resolve the issue.

1 – Don’t Convert SSRS 2008 reports to VS 2005 or VS 2008 client report! Go and drink a cup of coffee.

2 – Convert SSRS 2008 reports to VS 2005 or 2008 reports and get rid of reports which may face with issues. (For example don’t convert reports which contain tablix or newer 2008 schema items).

3 – Create client reports from the scratch for those which face with issue.

4 – Upgrading VS 2008 reporting schema which I don’t find a solution for it. (take a look at here)

5 – Using Report Viewer 2010 with Visual Studio 2008, this scenario may resolve your common issues but in my case it wasn’t enough.

6 – Convert SSRS 2008 reports to Visual Studio 2010 client reports. (I think in most cases it would be the best option). It will work fine because VS2010 use schema 2008 for reporting system. But unfortunately this will force you to buy a VS2010 edition!

So what’s the best approach to convert SSRS 2008 report to Client reports?

First approach – to get rid of some reports and create them from the scratch with schema 2005

Second Approach – To use Report Viewer 2010 inside Visual Studio 2008

Third approach – to upgrade VS 2008 to VS 2010 and enjoy conversion, but you have to upgrade your host framework too.

In my case second approach was good enough to resolve issue, but I used third approach. In your case it may be a little difference and you have to make a decision.

I was also looking for a solution which let me upgrade VS 2008 schema version from 2005 to 2008, (see here) but there were no solution.

How To Convert RDL files to RDLC files

.Net use RDLC files for reporting and SQL Server (Reporting Services) use RDL files for reports files. In this Article we will take a look at RDL and RDLC files and also a way to convert RDL files to RDLC files.

—————————————————————-

GNU Logo
GNU Logo

‪Title : How To Convert RDL files to RDLC files

‪Publish Date : 06/05/2010

‪Version : 1.0

‪Author : Nasser Hadjloo

‪Author Mail :  n.hajloo@gmail.com

‪Copyright (c) 2010 Nasser Hadjloo.

‪Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

‪with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

Comparison

1 – Both of them use a same XML schema called RDL (Report Definition Language). SQL Server Books Online documented this schema completely.

2 – “The ReportViewer control, which processes .rdlc files, ignores the <Query> element of RDL. If a report definition contains a query, the control will not process it. So A client report definition (.rdlc) file will only contain a query if it originated as a .rdl file.” MSDN said.

3 – DataSet and Data Source which used in RDLC and RDL files are totally different. RDLC (Client reports) use DataSet which actually is a DataTable and RDL (SQL Server Report) use DataSource which consist of a Data Source (actually connection String). Some Credential Information which used to access Database mentioned in Data Source and finally a SQL Command (StoreProcedure – Function …) or a Query which retrieve data from Database.

RDLC Report
RDLC Report

How To Convert RDL Files To RDLC Files

1 – As I mentioned before, both of these files are using RDL schema for representing items in a XML document, so in XML conversion there is no change. All the things you have to do, is to change RDL postfix to RDLC, commonly by Command Prompt.

2 – After that you need to Add this Report as an existing item to your Web project. (commonly in a report folder like “~/SystemName/Reports”)

3 – Next step is to create a dataset for this report, so create a DataSet File and put equivalent columns on it.

4 – At this time you need a method to retrieve data from Database and fill data on your DataSet.

5 – As you know, there is a Report Viewer control (actually an ActiveX) which get a Report and display itto user. So you need to create a page and use Report Viewer control on it. After including Report Viewer Control in the page, you need to assign your Report (RDLC file) to Report property of Report Viewer control. And also to assign your Dataset to DataSource property of ReportViewer.

6 – At the end you have to build project and check the results.

I wish this help you to convert RDL to RDLC files as easy as possible.

How to Extend SSRS Functionalities

SQL Server Reporting Services is one of the best Reporting Services which is available today; it has lots of functionalities and is easy to use. Today I’ll show you a way to extend SSRS functionalities.

—————————————————————-

GNU Logo
GNU Logo

‪Title : How to Extend SSRS Functionalities

‪Publish Date : 26/04/2010

‪Version : 1.0

‪Author : Nasser Hadjloo

‪Author Mail : n.hajloo@gmail.com

‪Copyright (c) 2010 Nasser Hadjloo.

‪Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

‪with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

There are sometimes which you cannot do, your desire work with SSRS default methods and Functions. For example CDate, IIF and etc are some of default SSRS commands. But what if you like to add your custom method to it? For example you need a method which take a Georgian date and return Persian Shamsi date. What can you do in these cases? Fortunately SSRS is a flexible service and you can easily extend it.

To extend SSRS, you need to create a class with desire methods, for example a class with a ConvertToPersiandate(dateTime georgiandate).

After that you have to build the project and Copy your DLL into following paths.

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\Bin
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin

These paths changed to following path in 2008 version

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\Bin
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin

The final step is to use it as a built-in SSRS command.
Just note that, you have to use complete Address for your method for example if you have these configurations

Name Space > Hadjloo.Web.Helpers.SSRS
Class Name > Converters
Methods in Class > ConvertToPersiandate(dateTime georgiandate) , ConvertToShortPersian (dateTime georgiandate) and etc

After That you have to add this DLL to your Report. To do this you should right click on the report and select Properties, then you should go to References tab and add this dll as a reference to your report.

SSRS 2008 Design Environment
SSRS 2008 Design Environment

Then in SSRS you have to use it like

=Hadjloo.Web.Helpers.SSRS. Converters. ConvertToPersiandate( First(MyGeorgianDate.value))

Note that in above case, First is a built-in command to get the first row value, and MyGeorgianDate is the DateTime field from the DataSet.

And also note that ConvertToPersiandate will have a red underline which is not important.

Merry Christmas and Hapy New Year

as you knew ,I’m blogging in english and stop writing Farsi, it is because I’m trying to find a job from another country and it is better to show my experience in english. it doesn’t mean that I’ll never write a persian document any more, but there will a document on a month.

—————————————————————-

GNU Logo
GNU Logo

‪Title : ‪Merry Christmas and Hapy New Year

‪Publish Date : 29/12/2009

‪Version : 1.0

‪Author : Nasser Hajloo

‪Author Mail : n.hajloo@gmail.com

‪Copyright (c) 2009 Nasser Hajloo.

‪Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

‪with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

any way we’re going to have a new year and finishing a good year. 2009 passed and I took too many experiences. it was bad and sometimes so good. but I want to start a real good year. in this year, I’ll

  •   finish JIRA translation.
  •   create at least 1 (or 2) Visual Studio (2010) add-ins
  •   read more about unicode
  •   work with a new dev team. (as I told, I’m looking for a remote job)
  •   desing a site for myself.
  •   write persian indeed document in english (e.g: introducing 9147 in english and vice versa)
  •   find a way to connect with Microsoft Windows localization center and suggest to put ISIRI 9147 keyboard layout as standard persian keyboard.
  •   work more and more with Microsoft Expression Suit.
  •   do more with WPF.
  •   Buy a new Desktop with core i7 cpu. (I’m one of Nehalem crazies. it’s really impressive.)
  •   changing my friendly reaction.
  •   collaborating with at least 1 (or 2) open source project
  •   publishing my resume on my peronal blog (site)
  •   do more connection with english bloggers.
  •   do more activity on asp.net and SSRS forum (or stackoverflow)
  •   try to start writing my first short hand book in english and persian (2 languages) it may be about unicode or something else.
  •   do more personal projects.

ok, I think it is enough for next year and wish you (specially persian bloggers) provide more persian or english documents and make it easier to find an answer.

at last wish you freedom and hope stand by me in next year. Merry Christmas and Hapy New Year

Open Source Unicode Converter

‪‪ as you may know I have some open source activity, and recently publish my first open source project in codeplex.

—————————————————————-

GNU Logo
GNU Logo

‪Title : Open Source Unicode Converter

‪Publish Date : 09/12/2009

‪Version : 1.0

‪Author : Nasser Hajloo

‪Author Mail : n.hajloo@gmail.com

‪Copyright (c) 2009 Nasser Hajloo.

‪Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

‪with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

‪in our company (where I’m working) we’re using Sql Server Reporting Services as reporting service system. we used SSRS 2005 and then upgrade to SSRS 2008 in this upgrading flow we face some problem and indeed to use unicode, where I get familier with unicode and its amazing features.

‪now 2 years passed and I feel that I should provide a powerfull tools for working with unicode, so I search for existing tool and I found

‪on codeplex, Khmr was so diffrent than I need, and fardis ( that leaded by one of my best friend – Afshar Mohebbi ) just cover persian range of unicode, and also afshar do not spent his time on this project any more (in my oponien), because of this I have create a Unicode converter for international reasons and international users.

Unicode Converter - Unicode Information Section
Unicode Converter - Unicode Information Section

‪Unicode Converter is a Free Open Source Software for converting to/from unicode and also getting information about a character.

‪Unicode Converter developed in C# 3.5 and provide 2 variant user interfaces, one for windows with WPF and one with Asp.net for Web.

‪WPF interface going to finish but web interface do not start yet, I think about 2 interface because WPF in limited to windows and a reall FOSS software should not depend on a platform so I provide a web interface for all users.

Unicode Converter - Keyboard Layout Section
Unicode Converter - Keyboard Layout Section

‪by the way in this couple of years I face with a huge issue and it was data input in any language, specially in IRAN most of users (i mean even expert users) use from default windows keyboard layout that is not a standard keyboard layout and all persians familier with ‘Yeh’ (ي – ی) and ‘Kaf’ (ك – ک ) and 4 – 5 & 6 and other numbers issue. that Persian Standard Keyboard Layout (IRISI 9147) resolve these problems in best way, so I put a section for Standards Keyboard Layout for all countries in this application when you select your country, all indeeded information about the keyboard layout will display.

‪ofcourse these information are not complete yet and I need your knoweledge to complete this information for all country, all you need to do is just extending Standards.XML in EnterpriseAppUnit project with your new country infromation and I believe that with your help we can made a better software.

Unicode Converter - Convert To Unicode Section
Unicode Converter - Convert To Unicode Section

‪Unicode Converter hosted by Codeplex , and have 4 project inside,

‪EnterpriseAppUnit : is the logic section of the application and provide some xml that contains characters unicode information.

‪Framework : is the base and common project to collaborate with all Projects, it contains exceptions and some other Base classes.

‪Portal : Web Interface of software

‪UnicodeConverter : WPF Windows interface of software

‪so I need your help to extend this project and if you have a little information (just for a country) please help us improve this application.

‪there are many of jobs to do, and you can see all of them in project Issue tracker.

‪any suggestion and help is appreciate.

‪Unicode Converter : http://unicode.codeplex.com

‪Regards Nasser hajloo

جاوا یا دات نت مسئله این نیست

Java
Java

چند وقتی هست که در یک شرکت که قالب پروژه هایشان را با جاوا می نویسند بصورت نیم وقت کار می کنم و همین امر باعث شد که این مطلب را بنویسم.

—————————————————————-

این مطلب زیر نظر مجوز GFDL منتشر می‌شود. و کلیه حقوق آن برای همگان آزاد است، بدین شرط که به کلیه شرایط موجود در مجوز GFDL ( که یک نسخه از متن انگلیسی مجوز GFDL در این محل و یک ترجمه غیر رسمی (فارسی) از متن مجوز GFDL که در مرداد ۱۳۸۳ توسط کاوه رنجبر تهیه شده است در این محل ) قرار دارد پایبند باشد.

GNU Logo
GNU Logo

عنوان مطلب : جاوا یا دات نت مسئله این نیست

بخش ثانی : ندارد

تاریخ انتشار : 06/05/1388 مطابق با 28/07/2009

شماره نسخه : نسخه یک

نویسنده : ناصر حاجلو

ای-میل نویسنده : n.hajloo@gmail.com

Copyright (c) 2009 Nasser Hajloo.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

خیلی وقتها وقتی کسی از من می پرسد که جاوا کار کنم یا دات نت ، باتوجه به شرایط فرد مذکور پاسخ دادن واقعا مشکل است. به همین دلیل در زیر کمی موضوع را باز می کنم ( توجه داشته باشی که موارد زیر برداشت شخصی من است ).

ازآنجا طیف بسار وسیع برنامه نویس های کشور افرادی هستند که به دانشگاه رفته‌اند، بسته به اینکه در دانشگاه به آنها دات نت آموزش داده شده یا جاوا به یکی از این دو زبان بدون اینکه از قابلیت ها و یا فلسفه شان آشنا باشند گرایش پیدا می کنند. و پس از مدتی کار با آن زبان خاص به شدت بر روی آن پلتفرم خاص تعصب پیدا می کنند و هر کسی که با پلتفرم دیگر کار می کند ، رقیب و بضا دشمن و نادان فرض می شود.

این مشکل از طرفی بخاطر ضعف اساتید در دانشگاه ها در شناساندن پلتفرم ها و موضع گیری شدید آنها درقبال زبان های برنامه نویسی است. خیلی وقتها در دانشگاه ها دیده می شود که استیدی که جاوا کار می کنند به دانشجویانی که با دات نت کا می کنند اجحاف می کنند و یا طرف را ر موضعی قرار می دهند که بین زبان های برنامه نویسی کلا تغییر شغل را انتخاب کند. (‌با الفاضی مانند … هم شد زبان برنامه نویسی… فلان چیز بدرد فلان کار می خورد یا نمی خورد…. فلانی ها که اصلا چیزی نمی فهمند و .. ، این نکته کاملا بصورت دوطفه قابل لمس است.)

.netFramework
.netFramework

فارغ التحصیلان دانشگاهی هم از آنجا که در دانشگاه بدون دانش و بدون حق انتخاب یکی از دو پلتفرم را آموخته اند شروع می کنند به کار و توسعه در پلتفرم مخصوص به خودشان بدون اینکه اوقاتی را صرف تحقیق ومطالعه بر روی آموختن قابلیت ها و مزایای پلتفرم ها دیگر بی‌اندازند. و این بی دانشی به حدی زیاداست که معمولا از کوچکترین قابلیت های زبان دیگر هم کوچکترین اطلاعی ندارند ونوشتن یک برنامه ساده در زبان دیگر حکم قصاص برای آنها دارد.

به هر روی و از آنجا که بحث بیش از آنچه که می ادیشیدم به درازا کشید موارد زیر را متذکرم شوم. و از سایر دوستان هم خواهش می کنم که اگر مواردی به ذهنشان می رسد در بخش نظرات آن را با ما قسمت کنند.

Cross Platform : بسته بهاینکهبرنامه شما کجا باید اجرا شود باید اقدام به انتخاب کنید. مهمترین مزایای جاوا این است که کاملا آزاد است و در هر پلتفرمی اجرا می شود. گرچه دات نت هم با راه اندازی مونو قصد دارد به چنین هدفی برسد اما هنوز نمی توان بر موفقیت آن یقین داشت. از طرف دیگر بزرگان برنامه های آزاد برای دات نت کارها بستری با عنوان Portable .net مهیا کردند که مانند جاوا در هر پلتفرمی اجرا می شود اما با کتابخانه‌‌های بسیار کم و محدود.

Open Source : جاوا یک پروژه کدباز است و این مشخص می کند که آینده خوبی دارد ، و از طرفی شرکت SUN دانلود آن را برای داخل ایرانی ها کاملا ممنوع کرده و شما با IP ایرانی قادر به دریافت جاوا از سایت SUN نیستید.  از طرف دیگر مایکروسافت هم پس از دات نت ۳۰ کل فریم ورک خودش ر بصورت کدباز در اختیار عموم قرارداده و سایر کنترلهای الحاقی آن را هم بصورت کدباز پیش می برد که از قافله عقب نماند.

ایده تجاری (business Plan) شرکت : بسته به اینکه شما می خواهید در دنیای Copy Rightی ها و یا Copy Left ی ها زندگی کنید باید اقدام به انتخاب یکی از این دو زبان بکنید. جاوا بای برنامه های آزاد و کدباز و دات نت برای برنامه های تجاری با مجوز مناسب تر هستند.

رابط کاربری و ارتباط با کاربر : عموم برنامه های جاوا دارای فر های ضعیفتری نسبت به همتا های دات نتی خود هستند . جاوای ها مجبورند که زمان بسیار بشتری را برای طراحی رابط کاربری صرف کنند تا دات نتی ها. معمولا یک برنامه جاوایی با رابط کاربری قوی زمان، هزینه و کار بیشتری می برد تا همان رابط کاربری در دات نت. ( توجه کنید که بحث کنترل های الحاقی را در این قسمت داخل نکنید )

برنامه نویسی شی گرا : جاوا از اولین بان های شی گرا بود و خیلی ها به همین دلیل عاضقجاوا هستند در حالی که دات نت اصولا ر آن زمان وجود نداشت و C++ که هنوز هم عاشقان خود را دارد یکه تاز میدان بود. اما با ورود دات نت معادلات قدرت کمی تغییر کرد. زبان هایی مانند پایتون . روبی و سی شارپ به سرعت شی گرایی را در قالب خودشن گسترش دادند و هرکدام نسبت به دیگری در پیاده سازی تفاوت هایی را قایل شدند.

هزینه و مجوز : برنامه های دات نتی با هزیه های گزاف تولید می شوند بر خلاف جاوایی ها. ی بخش از این هزینه صرف تهیه IDE و پایگاه داده وسایر افزونه های مورد نیاز می شود که در دات نت بسیار گران قیت هستند و به همین دلیل برنامه نویس های دات نتی معمولا نسب به جاوایی ها حقوق کمتری می گیرند. چون در دنیای جاوا شما برای هیچ چیزی لازم نیست هزینه بپردازید، تقریبا نسخه رایگان همه چیز در دست است و شما به خوبی م توانید با آن کار کنید. و بههمین دلیل برنامه نویس های جاوا حقوق بیشتری می گیرند چون هزینه تولید نرم افزار در جاوا کمتر است.

IDE و سیستم های گزاش گیری : در دات نت Visual Studio چنان قدرت نمایی می کند که حتی سرسخت ترین هواداران جاوا هم آرزو دارند روزی با چنین IDE یی کار کنند. به همین دلیل به مزایای فوق العاده آن اشاره نمی کنم. از طرفدیگر در دنیای جاوا هنوز یک IDE قدرتمند ظهور نکرده. NetBeansIntellij IdeaeClipse و سایر آنها هنوز آن قدر قوی نشدند تا رقیب را از صحنه بدر کنند. خیلی ها با توجه به عاداتی که دارند اقدام به انتخاب می کنند. و حرفه‌ای تر ها از eclipse خود این موضوع عدم کاربرپسند بودن IDE های جاوا ر بخوبی نشان میدهد. از طرف دیگ سیستمهای گزارش گیری جاوایی مثل JBoss ( اگر اسمش را صحیح نوشته باشم ) هنوز نیمی از قدرت Reporting Services و یا حتی Crystal Reports را هم ندارند. گرچه در بعضی از موارد برتری هایی به این دو سیستم دارند اما در کل ضعیف تر هستند.

یکپارچگی : برنامه های دات نتی در هر بستری که باشند ( وب – ویندوز – موبایل و …) بصورت وحشتناکی یکپارچه هستند برعکس برنامه های جاوایی.  از طرف دیگر برنامه هی جاوایی بخصوص در زمینه موبایل ( بخاطر Cross Platform بودن ) با دردسر بسیار کمتری اجرا می شوند.

موارد بسیار دیگری هم هست که می توان به آنها اشاره کرد که بخاطر به درازا کشیدن بحث از بیان آنها خودداری می کنم.

رفع مشکل Trusted Assembly در Reporing Services

یک مشکلی که در Report های کلاینتی Reporting Services وجود دارد آن است که اگر شما بخواهید از یک 3rd party dll در گزارش استفاده کنید  ( مثلا برای تبدیل تاریخ یا غیره ) به یک پیغام خطای The report references the code Module ‘Hajloo.Localization, Version=1.0.0.0, Culture=neutral, Publickey Token=b77a5XXXXXXXX’, which is not a trusted assembly برخورد می‌کنید. در زیر نحوه برطرف کردن این خطا را آورده‌ام.

—————————————————————-

این مطلب زیر نظر مجوز GFDL منتشر می‌شود. و کلیه حقوق آن برای همگان آزاد است، بدین شرط که به کلیه شرایط موجود در مجوز GFDL ( که یک نسخه از متن انگلیسی مجوز GFDL در این محل و یک ترجمه غیر رسمی (فارسی) از متن مجوز GFDL که در مرداد ۱۳۸۳ توسط کاوه رنجبر تهیه شده است در این محل ) قرار دارد پایبند باشد.

GNU Logo
GNU Logo

عنوان مطلب : رفع مشکل Trusted Assembly در Reporing Services

بخش ثانی : ندارد

تاریخ انتشار : 20/04/1388 مطابق با 11/07/2009

شماره نسخه : نسخه یک

نویسنده : ناصر حاجلو

ای-میل نویسنده : n.hajloo@gmail.com

Copyright (c) 2009 Nasser Hajloo.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

این خطا به آن علت است که چون گزارش‌های کلاینتی باید بصورت Open Format ایجاد شوند ( یعنی به صورتی که بدون نیاز به هیچ چیز خارجی و یا بدون به خطر انداختن سیستم کلاینت اجر شود ) بنابراین تولید کننده گزارش باید dll ی را که از آن ر تولی گزارش استفاده کرده، تضمین کند و عواقب بعدی آن را ( که ممکن است به در معرض خطر قرار گرفتن سیستم کلاینت شود را ) بپذیرد.

به همین دلیل پیغام زیر ( که در بالا هم آوردم ) نمایش داده می‌شود.

The report references the code Module ‘Hajloo.Localization, Version=1.0.0.0, Culture=neutral, Publickey Token=b77a5XXXXXXXX’, which is not a trusted assembly

برای رفع این مشکل تنها کاری که باید اجام دهید آن است که بروید و در صفحه‌ای که Report Viewer را برای نمایش گزارش قراردهاید قطعه کد زیر را جهت تضمینdll خودتان بنویسید.

this.reportViewer1.LocalReport.AddTrustedCodeModuleInCurrentAppDomain(“Hajloo.Localization, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b77a5XXXXXXXX”);

نهایتا با قراردادن قطعه کد بالا مشکل برطرف می‌شود.

خود من جواب این سوال را در وبلاگ محمد شرف پیدا کردم که این بخش که من اشاره کردم صرفا قسمت کوتاهی از نوشته محمد است. توصیه می کنم مطلب کامل او را مطالعه نمایید.

همچنین یک مطلب مرتبط دیگر هم اینجا هست.