دانلود کامپپوننت‌های شرکت تلریک | Telerik UI for WinForms 2018 R3 SP1 (2018.3.1016) Retail

کامپپوننت‌های شرکت Telerik شناخته‌شده‌ترین مجموعه برای برنامه‌نویسان دات‌نت می‌باشد که با استفاده از این مجموعه‌ی بسیار متنوع و کاربردی، از طراحی انواع واسط‌های کاربری تا گزارش‌گیری پیشرفته و حرفه‌ای برای سیستم‌عامل‌ها و پلت‌فرم‌های مختلف امکان‌پذیر خواهد بود. مجموعه‌ی کامل کامپوننت‌های دات‌نت این شرکت با عنوان Telerik DevCraft شناخته می‌شود و کامپوننت‌های مربوط به HTML5 با نام Kendo UI عرضه می‌شوند؛ همچنین Telerik Platform عنوان کلی کامپوننت‌های مربوط به ابزارهای موبایل می‌باشد.

--

Telerik UI for WinForms 2018 R3 SP1 (2018.3.1016) Retail Key Features: Document Processing Process the most common text, spreadsheet, and PDF file formats without any dependencies on external libraries. Professional-Looking Themes Brush up your app with a modern and professional look and feel fit for any scenario. Complete Set of Features and Controls Comprehensive toolbox of 120+ WinForms UI controls to help you develop everything. Unrivaled Performance ...

  ادامه مطلب ...

تبدیل پروژه وب سایت به وب اپلیکیشن در سی شارپ | Converting a WSP to a WAP

Converting a Web Site Project to a Web Application Project

Differences between Web Site Projects (WSP) and Web Application Projects (WAP) are highlighted in blogs such as this one. Based on that, if you feel a WAP would be better for your particular needs than a WSP, but have already created a WSP, you may be asking yourself, “Can I convert my WSP into a WAP, without starting from scratch?”.

This posting explains how to convert an existing Web Site Project to a Web Application Project in Visual Studio 2010. The most striking differences to a Web Site Project are that WAPs have a project file to include and exclude files, and compile to a single assembly.

The guidelines below include several of the basic steps detailed in the Walkthrough: Converting a Web Site Project to a Web Application Project in Visual Studio. This is an excellent topic to review as it discusses some specific issues you may encounter which were discovered in previous versions of Visual Studio (VS). Please keep in mind while reading it that it is based on a WSP to WAP conversion using previous versions of Visual Studio...

   ادامه مطلب ...

ASP.NET Web Deployment using Visual Studio: Deploying to Test

This tutorial series shows you how to deploy (publish) an ASP.NET web application to Azure App Service Web Apps or to a third-party hosting provider, by using Visual Studio 2012 or Visual Studio 2010. For information about the series, see the first tutorial in the series.

Overview

This tutorial shows how to deploy an ASP.NET web application to IIS on the local computer.

When you develop an application, you generally test by running it in Visual Studio. By default, web application projects in Visual Studio 2012 use IIS Express as the development web server. IIS Express behaves more like full IIS than the Visual Studio Development Server (also known as Cassini), which Visual Studio 2010 uses by default. But neither development web server works exactly like IIS. As a result, it's possible that an application will run correctly when you test it in Visual Studio, but fail when it's deployed to IIS.

You can test your application more reliably in these ways:

1. Deploy the application to IIS on your development computer by using the same process that you'll use later to deploy it to your production environment. You can configure Visual Studio to use IIS when you run a web project, but doing that would not test your deployment process. This method validates your deployment process in addition to validating that your application will run correctly under IIS.
2. Deploy the application to a test environment that is nearly identical to your production environment. Since the production environment for these tutorials is Web Apps in Azure App Service, the ideal test environment is an additional web app created in Azure App Service. You would use this second web app only for testing, but it would be set up the same way as the production web app.

Option 2 is the most reliable way to test, and if you do that, you don't necessarily have to do option 1. However, if you are deploying to a third-party hosting provider option 2 might not be feasible or might be expensive, so this tutorial series shows both methods. Guidance for option 2 is provided in the Deploying to the Production Environment tutorial.

For more information about using web servers in Visual Studio, see Web Servers in Visual Studio for ASP.NET Web Projects.

Reminder: If you get an error message or something doesn't work as you go through the tutorial, be sure to check the troubleshooting page.

   ادامه مطلب ...