Hello World:解剖 ASP.NET 项目

ASP.NET Core----基础学习01----HelloWorld---创建Blank空项目 1. 创建新项目--方式一: blank 2. 程序各文件介绍(Project name :ASP.Net_Blank) (1)launchSettings.json 启动方式的配置文件 (2)appsettings.json 基础配置file参数的读取 (3)Program.cs 程序启动的入口文件 3. 简单改造---通过Startup.cs文件获取程序的Name,并返回页面显示 4.简单改造:将appsettings.json 文件中读取到的内容传递到页面显示 5.程序从不同file源读取数据的顺序 阅读详情

Hello World: An Anatomy of an ASP .NET Project

by Kaushal Sanghavi

Introduction

Ever since Kernighan and Ritchie wrote a program to display "Hello World" in the C language, programming has never been the same. I have learnt and programmed a variety of new languages since then, and my first attempt at each new programming language has been to greet the world with a "Hello World". ASP .NET is not just a new revision of ASP. It is not ASP 4.0. It is a completely new paradigm and a new programming model and language. What better way to be introduced to this language than with a Hello World?

In this article, I will attempt to write a simple "Hello World" and explain all the code that goes behind this. ASP .NET generates a lot of code and files for you to support the notion of a Web Application, and we will dig into the details of an ASP .NET project.

A note about the attached code is due here. Due to the multiple files that VS .NET creates, the references to drives, and folders, it turned out to be very difficult for me to zip up all the code and link it to this document. It would have been next to impossible for someone to download this code and get it working "out of the box". As a result, I am only attaching the HelloWorld.aspx and HelloWorld.vb files and I would recommend you create an empty ASP .NET project and add these files to your project. A zipped version of the source code is available for download from here.

How to Create an ASP .NET Project

Creating an ASP .NET project is fairly simple. You will need to have the Beta 1 version of Microsoft Visual Studio .NET. In reality, you don't need this tool, it is possible to open up your favorite editor and start typing, but VS .NET provides a whole lot more than your simple Notepad. I will focus on creating ASP .NET projects using Microsoft VS .NET Beta 1. In order to create an ASP .NET project, follow these simple steps.

  1. Chose "New Project" from VS .NET IDE.
  2. Under the "Project Type", select "Visual Basic Projects" and chose the "Web Application Template".
  3. Enter the name of your ASP .NET project (ASPHelloWorld in this case) and voila! You have just created your first ASP .NET project.
  4. Rename the WebForm1.aspx to a more meaningful name. In this sample, I have renamed it to HelloWorld.aspx and this is how I will refer to it in this article.

Files generated by VS .NET

When you create an ASP .NET project, VS .NET by default creates the following main files for you. You should be able to view and open these files using the Solution Explorer. Let me start with a list of these files and a quick description of this. In the next section, I will deep deeper into each file and try to explain each in more detail.

ASPHelloWorld.disco
Used for dynamic discovery of Web Services
Config.web
Contains the configuration settings for this Web Application
Global.asax
Similar to the Global.asa file. Contains global events for this Web Application
Global.vb
This contains the event handling code corresponding to the Global.asax
HelloWorld.aspx (by default, this file is called WebForm1.aspx)
Blank by default. This is where your ASP/HTML controls go in.
HelloWorld.vb
This contains the event handling code for the corresponding .aspx file
Styles.css
Style sheet that can be used across the application

In addition to these, VS .NET also creates the following files that are used internally by VS .NET. These contain details about the project settings etc. I would recommend you to open these in notepad and view them in order to understand how VS .NET uses these, but be careful not to modify these. Modifying these files could cause VS .NET to not recognize your project and not be able to open the solution.

ASPHelloWorld.sln ASPHelloWorld.suo ASPHelloWorld.vbproj ASPHelloWorld.vbproj.webinfo

Digging into Code

Now that we have covered the basics, its time to dig into the real code.

Please enter your name

This is what the HelloWorld webform looks like. It asks you for your name and then proceeds to greet the world "Hello World" followed by your name in parenthesis.

Hello World (by Kaushal)

Now that we know what the code does, lets dive into the code.

HelloWorld.aspx Details

Lets start with digging into the details of the .aspx file that has been generated. Keep in mind, I have not written a single line of HTML for this. This is a very VB-sque experience. VS .NET provides a standard Toolbox that contains WebForm controls, HTML controls, Server controls etc, and building the UI is as simple as dragging and dropping these controls and setting their properties in the Properties window (again a feature inspired by the VB 6.0 Properties window). I will take certain sections of the generated code and discuss this. If you want to see how these sections fit together, or would like to look at the code in its entirety, I would suggest that you open the code (from the zip file) in VS .NET and follow along.

Page Level Attributes

The first thing you will notice when you open up the HelloWorld.aspx in an editor is this line:


<%@ Page Language="vb" Codebehind="HelloWorld.vb" Inherits="ASPHelloWorld.HelloWorld"%>

This statement describes certain page level attributes for this aspx file. ASP .NET introduces a new syntactical construct <%@ ... %> which is used for specifying attributes. Every aspx file will have a statement similar to this that describes attributes such as the class that contains the event handler code, the name of the file containing the code, the language etc. This is necessary because ASP .NET cleanly distinguishes the presentation from the code. The aspx file only contains the HTML tags and server controls, while all the code needed to process the events that are fired by these controls are contained in a separate file. This allows the separation of effort between graphic designers who could be building beautiful pages and software engineers who could be writing beautiful code. The current ASP model mixes the HTML tags and controls with code, and anyone trying to read, maintain, or debug a 5000 line ASP file can attest to this.

There are too many ASP .NET attributes that can be covered here, so I will concentrate on some of the most important ones.

  • Language: This tells the ASP .NET compiler (yes! ASP .NET is compiled) that the language used is VB. Currently ASP .NET supports VB, JavaScript and C#.
  • CodeBehind: Determines the file that contains the event handling code for this aspx file.
  • Inherits: Determines the class that will contain methods to handle events on this page.
  • AspCompat: Determines whether this page is backward compatible with ASP.
  • Buffer: Determines whether page level buffering is enabled.
  • EnableSessionState: Determines whether SessionState is enabled.
  • ErrorPage: Determines the URL to be redirected to in the event of an unhandled exception.

ASP .NET Controls

These controls form the heart of ASP .NET. These are rich server side controls that can be used to build a powerful UI on the web similar to Windows based user interfaces.

<asp:label id=lblName runat="server">Please enter your name
       asp:label><asp:label id=lblHello runat="server">
        asp:label><asp:textbox id=txtName runat="server">
         asp:textbox><asp:button id=btnSubmit runat="server" Text="Submit">
          asp:button>

As you can see in the code above, the HelloWorld example uses four ASP .Net controls. Note the "asp:" prefix for each control. This is what distinguishes ASP .NET controls from standard HTML controls. We use two labels to display static messages, a textbox to allow the user to input the name, and a button that will be used as a submit button. These server side controls fire events very similar to the way windows controls fire events in a VB 6.0 program. These events can be trapped and code can be written to take action depending on what event is fired for what control. This offers much more functionality and flexibility that standard HTML controls. Currently ASP .NET supports the following types on server side controls:

HelloWorld.vb Details

This file contains the code that supports the ASP .NET controls from the HelloWorld.aspx file. This code is identical to VB code, in fact it is VB code. Lets start with some code excerpts, again I would recommend you to have VS .NET open and the project loaded and have the code in its entirety.

Importing Namespaces

Imports SystemImports System.ComponentModel.DesignImports System.DataImports System.DrawingImports System.WebImports System.Web.SessionStateImports System.Web.UIImports System.Web.UI.WebControlsImports System.Web.UI.HtmlControlsImports Microsoft.VisualBasic

.NET introduces the concept of namespaces. Namespaces are essentially a collection of types and functionality. VB .NET introduces the Imports statement that is used to references assemblies outside your project. Most of the namespaces that are imported here are from the System namespace, but you could import any namespace as long as it lives in a public assembly. Importing a namespace is similar to adding a reference to a DLL in VB 6.0. It allows you to access the public elements (classes, functions, methods, etc) in that namespace. In our example, VS .NET automatically imports these namespaces to add support for Web Controls. You could easily add to this default list. For example, if you wanted to add XML manipulation support to your code, you can add the "Imports System.XML" line to your code.

HelloWorld Class

Public Class HelloWorld    Inherits System.Web.UI.Page    Protected WithEvents lblName As System.Web.UI.WebControls.Label    Protected WithEvents btnSubmit As System.Web.UI.WebControls.Button    Protected WithEvents txtName As System.Web.UI.WebControls.TextBox    Protected WithEvents lblHello As System.Web.UI.WebControls.Label    Public Sub btnSubmit_Click(ByVal sender As Object, ByVal e As                                                       System.EventArgs)        txtName.Visible = False        lblName.Visible = False        btnSubmit.Visible = False        lblHello.Text = "Hello World (by " + txtName.Text + ")"        lblHello.Visible = True    End Sub        Protected Sub WebForm1_Load(ByVal Sender As System.Object, ByVal e                                                   As System.EventArgs)        ' Evals true first time browser hits the page        If Not IsPostback Then            lblHello.Visible = False        End If    End Sub    End Class

VB .NET is a purely object oriented language. (Of course, you could still write non-OO code and not use the OO features that VB .NET provides, but that defeats the purpose). Thus, all the code in the above figure resides in a class definition. We declare a public class named HelloWorld that forms the backbone of our HelloWorld.aspx page. All the code behind an ASP .NET page is derived from the System.Web.UI.Page class, which contains the framework code for ASP .NET pages.

The four controls that are used on this page as defined as protected members of this class and the type of each controls is referenced from the System.Web.UI.WebControls namespace. The WithEvents keyword is used to specify that the object variables will respond to triggered events. In addition to these data members, you could add any data members that you may want to and specify the access modifiers (public, private, protected) for these data members.

The crux of the logic in an ASP .NET page will live in the event handling code for one or more server side controls. In our trivial example, we handle two events. The first event is for the page load in which we simply hide the label that will be used to display the Hello World message. When the user clicks on the Submit button, this will fire the event handled by the btnSubmit_Click method. In this method, we simply read the value entered in the textbox and display the Hello World message. We also hide some of the controls that are no longer needed. This is all the code that is necessary to support our Hello World sample.

Config.web Details

With ASP .NET, Microsoft introduces the notion of a human readable and modifiable configuration file for Web Applications. Those of you who have dealt with the IIS Metabase know that maintaining and modifying configuration wasn't exactly a breeze. ASP .NET introduces an XML file based configuration scheme, which is extremely powerful. The amount of details in the file warrants a whole new article, so I will focus only on some of the settings that are generated by VS .NET by default.

<compliation  debugmode="true" /><customerrors mode="Off"  /><trace     enabled="false"     requestlimit="0"     pageoutput="false"     tracemode="SortByTime"/><sessiostate     inproc="true"     usesqlserver="false"     cookieless="false"     timeout="20"     server="localhost"     port="42424"/>

These are some of the default settings generated by VS .NET.

Compilation Mode
This settings tells the.NET compilers to generate debug information for the .aspx files. This is usually set to True in the development cycle, but once the application is moved over to Production, this should be set to false. Turning off this setting greatly improves the runtime performance of the system.
Custom Errors
ASP .NET introduces a declarative way of exception handling. By turning on CustomErrors, it is possible for ASP .NET to redirect the page to an error page whenever an unhandled exception occurs. Further, it is possible to define separate custom error pages for each HTTP error code that could occur. This is a very powerful feature that can avoid ugly errors being shown to the user.
Trace
Those of you who have tried debugging traditional ASP programs probably used more Response.Write statements than you cared to. ASP .NET introduces an elegant way of adding trace/debug information that is consistent and configurable. By turning on Trace in the Config.web file, it is possible to have Trace statements throughout the code that can be turned on or off by this switch. Further, you can determine where the trace output is displayed and have levels of tracing such as Fatal or Informational.
Session State
There have been so many occasions where I wished I could use the ASP Session variables, only to realize that the application will be running on a WebFarm without server affinity. In these cases, you end up not using the ASP Session, or you come up with your own implementation of session state. ASP .NET introduces a new way of handling Session data. You could use session the way it is used currently, or you could use a separate process (on the same machine or a separate machine) to store session data. You could even persist session data in a database. Again, this is entirely declarative and you don't have to change a single line of code to support this. This is a very powerful way to handle session data without having to implement a custom implementation.

Conclusion

When I wrote my first Hello World in C, I used the following code

#include 
      
       int main (){	printf ("Hello World");	return 1;}
      

My next Hello World was in C++, which took a few more lines, and then I moved over to Windows Programming in SDK, Windows Programming in MFC, COM Programming, COM Programming in ATL and slowly the complexity of the Hello World programs kept increasing. The same holds true for the Hello World that I wrote for ASP .NET. As you can see from the above code, the code needed to write a Hello World example takes far more than 7 lines. However, most of the code that is present is to support the framework and the plumbing needed to build complex real world applications. This is certainly true for ASP .NET, which is a huge huge improvement over traditional ASP, and Microsoft has brought VB-like development to the web. In future articles, I will dig deeper into the guts of ASP .NET.

Happy .Netting !

Additional Information:




C#/.NET学习实战指南:从零搭建环境到项目部署的完整路径 在软件开发领域,掌握一门主流编程语言如C#及其生态系统.NET,是构建企业级应用的核心技能。其原理基于公共语言运行时(CLR)和跨平台框架设计,技术价值体现在高效开发、性能优化和强大的生态支持上,广泛应用于Web API、微服务、桌面应用和工业控制等场景。对于初学者和进阶开发者而言,如何系统性地学习并实践是关键。本文聚焦于C#/.NET实战学习路径,针对常见痛点如环境配置、依赖管理、项目调试等提供解决方案,并融入WebApi接口开发和Docker容器化部署等热词,帮助开发者将理论知识转化为可运行的代码能力, 阅读详情

相关推荐

手写轻量级 ASP.NET 服务框架:深入管线、Handler 与 Module

ASP.NET 管线是请求处理的核心机制,其本质是一系列可订阅的生命周期事件链;HttpHandler 承担业务逻辑执行职责,HttpModule 则负责横切关注点(如认证、日志、重写)的拦截与调度。这种职责分离设计赋予了极高的可预测性与定制自由度,尤其适用于统一网关、协议适配、深度监控等工程场景。相比 MVC 的高抽象封装,基于原生管线构建的轻量级服务框架,能精准控制序列化方式、URL 路由时机与请求流劫持点,让开发者真正掌握从 IIS 接入到响应输出的全链路。本文即围绕 ASP.NET 管线与 Http

dianlu5775的博客 586

【ASP.NET】Win7下ASP.NET的配置,Helloworld,发布网站

Win7下配置ASP.NET环境与配置ASP(VbScript)极其类似,毕竟大家都是微软的产品,在2003年ASP.NET诞生之前,用Windows做服务器来写网页的,几乎清一色都是ASP。 其实Win7下配置ASP.NET环境是极其简单的,没有网上说的这么复杂。 一、IIS服务器的开启 在Win7下配置ASP.NET,前几步与配置ASP(VbScript)是相同,都是要开启IIS服务

编程记录,亲测有效 4467

ASP.NET MVC底层原理与HTTP契约解析

MVC模式本质是HTTP请求与.NET对象之间的结构化映射协议,其核心在于路由匹配、模型绑定、视图解析三大机制如何严格对齐HTTP语义。理解RouteData如何将URL路径段确定性地分解为Controller/Action/参数,掌握DefaultModelBinder在ValueProvider链中按优先级提取表单、路由、查询参数的执行逻辑,才能真正驾驭高并发、安全合规、可测试的Web应用构建。这些原理在ASP.NET Framework与Core中数学同构,仅实现载体不同。本文聚焦MVC内核中被现代抽

dejz8829的专栏 606

.NET应用程序--Helloworld(C#)

.NET--HelloWorld

DXB2021的博客 1208

老赵点滴:一个以人本认知驱动的.NET技术博客方法论

技术博客的本质是知识传播系统,其有效性取决于是否契合人的认知规律、技术演进逻辑与工程实践需求。在.NET生态中,‘人-技术-程序员’三位一体的内容架构正成为高质量技术传播的新范式——它用真实业务场景激活问题图式,以领域建模替代工具链崇拜,并通过本地调试、CI验证、生产灰度构建全链路可信闭环。这种设计不仅提升中级开发者解决隐性痛点的能力,更推动从CRUD编写者向系统设计者跃迁。结合C#异步状态机、ASP.NET Core中间件等典型热词,该模式为.NET技术内容生产提供了可复用、可验证、可传承的方法论基础。

dejz8829的专栏 518

HttpHandler与HttpModule核心区别及迁移指南

HttpHandler和HttpModule是ASP.NET请求管道中两类关键扩展机制,前者负责终结请求并生成响应,后者通过订阅生命周期事件实现横切逻辑。其设计本质源于对HTTP请求处理流程的分层抽象:Handler对应‘执行单元’,Module对应‘拦截增强’。这种分离支撑了鉴权、日志、缓存等通用能力的复用与解耦,构成传统Web Forms/MVC架构可维护性的底层基础。随着.NET Core演进,二者被Middleware(模块化中间件)和Endpoint Routing(轻量终结点)以更透明、可测试的

didi9310的博客 635

【ASP.NET】Hello World

ASP.NET Core 是 ASP.NET 的下一代版本,建立在.NET Core 之上,包括 ASP.NET Core MVC(用于构建 Web 应用)和 ASP.NET Core Web API(用于构建 Web 服务)等技术,是一个平台,包括 .NET Framework、.NET Core、ASP.NET、C#等,可以构建桌面、Web、移动应用等应用程序。是 .NET 平台的一个特定组件,是用于构建 Windows 应用程序的框架,只能在 Windows 操作系统上运行,

Awt_FuDongLai的博客 1388

二 ASP.NET MVC 第一个程序 hello world

二 ASP.NET MVC 第一个程序 hello world

asp.net创建helloWord

1、前端建立asp标签,可选label 2、后端进行赋值 name1.Text = (string)DS.Tables[0].Rows[1]["D_Name"]; 注意ID号对应

taotaox的专栏 1000

从‘全步’到‘微步’:一张图看懂步进电机细分控制,选对模式让你的项目更丝滑

本文深入解析步进电机细分控制技术,从全步到微步的演进过程,帮助工程师根据项目需求选择最优控制模式。通过对比不同细分等级的性能特点和应用场景,提供3D打印、实验室自动化等领域的黄金配置方案,实现更精准、平稳的电机控制效果。

weixin_29290259的博客 471

nCode:GlyphWorks案例教程一

nCode GlyphWorks案例一Comparing Frequency Content of Two Different Tests案例文件目标配置选择数据 Comparing Frequency Content of Two Different Tests 在本案例中,我们将比较来自两个不同测试的六个加速计通道的频率内容。将三轴加速度计放置在车辆的左前角和右前角,然后分别在两个不同的试验路面上行驶12分钟以上。 案例文件 此案例的文件(采用nCode DAC格式)位于nCode安装目录下的\demo

追月行的博客 1万+

C#程序结构解析:从Hello World到命名空间与Main方法

理解编程语言的基础结构是掌握其开发能力的关键,这涉及到程序如何组织、编译和运行的核心原理。在C#和.NET平台中,程序通过命名空间进行逻辑分层,使用类作为功能封装的基本单元,并通过Main方法作为执行入口点。这种结构设计不仅保证了代码的可维护性和可扩展性,还为构建各类应用程序提供了统一的基础框架。从简单的控制台应用到复杂的Web开发,如ASP.NET Core Razor Pages,都建立在这一基础结构之上。本文以Hello World程序为起点,深入解析C#程序的骨架,帮助开发者建立扎实的编程基础,并平

weixin_34167819的博客 381

从jieba分词到BERT-wwm——中文自然语言处理(NLP)基础分享系列(12)

今天是本系列的最后一期,完整代码呈现Huggingface transformers平台上微调BERT-wwm-ext的过程方法。

weixin_49518391的博客 3766

ASP.NET技术写作手记:从基础细节到认知地图

ASP.NET作为经典的Web开发框架,其核心价值不仅在于语法和API,更在于对请求生命周期、状态管理、配置机制等底层原理的深刻理解。掌握Request.Params取值顺序、HttpHandler映射规则、Cache穿透防护等关键细节,是避免线上故障的基础能力;而将这些知识点组织成可检索、可复用的‘技术认知地图’,则体现了工程化写作的真正价值。这类内容既服务于初学者快速定位问题,也支撑资深开发者构建系统性调试能力。本文聚焦ASP.NET中那些文档未明说、但生产环境高频踩坑的技术细节,结合真实故障排查与性能

unixboy 484

利用setEcoMode优化innovus中的ecoAddRepeater批量操作效率

本文详细介绍了在Cadence Innovus工具中,如何利用setEcoMode命令的batchMode参数,显著提升ecoAddRepeater命令在批量插入buffer或inverter时的操作效率。通过合并重复的初始化和数据库更新开销,该模式可将大规模时序修复操作的执行速度提升数倍,并提供了完整的脚本示例与最佳实践,帮助后端设计工程师优化ECO流程。

mango的博客 515

深入解析机器人软件开发中的核心:状态机管理(FSM)—— 理论、实践与优化

状态机(FSM)是机器人软件开发中管理复杂行为逻辑的核心工具,广泛应用于导航、任务执行、故障处理等场景。本文系统探讨状态机的基础理论(定义、要素)、主流设计模式(经典FSM、分层状态机HSM、行为树BT),以及工业级实现方法(代码架构、线程安全、调试技巧)。通过移动机器人导航和机械臂任务执行的案例,分析分层状态机的实际应用,并总结常见陷阱(如状态爆炸、阻塞操作)与优化策略(异步化、事件过滤)。

郑伟强dev的专栏 292

手写ASP.NET MVC框架:5大核心模块原理与实现

Web框架的核心在于请求处理管道的设计与控制,其本质是HTTP生命周期的结构化编排。理解路由分发、控制器激活、模型绑定、动作执行和视图渲染这五大机制,是掌握现代MVC架构的基石。本文以轻量级C#实现为载体,剥离System.Web依赖,聚焦可调试、可验证的底层逻辑,深入剖析PathSegment树匹配、Expression Tree编译构造、显式模型绑定等关键技术决策。通过裸金属式HTTP监听与接口契约驱动的模块解耦,揭示框架如何将URL路径转化为可执行代码,并安全可控地生成响应。适合希望突破API黑箱、夯

diaoqi6581的博客 525

垂类大模型 研发方向与具体方案调研

领域知识库加上通用大模型,针对通用大模型见过的知识比较少的问题,利用向量数据库等方式根据问题在领域知识库中找到相关内容,再利用通用大模型强大的summarization和qa的能力生成回复,完成本次垂直大模型研发。目前很多企业希望将大模型的能力应用到企业内部当中,但很多通用大模型只是一个预训练模型,其所能回答的知识主要来源于互联网上公开的通用知识库,对于部分垂直领域和企业内部的私有知识库的问答,给出的回答。:垂类大模型的效果与底座性能息息相关,研发垂类大模型第一步就是确定开源大模型解决方案。

风吹落叶的博客 3332

.NET十年演进:从Core 1.0到.NET 10的底层重构全景

.NET 是微软推出的跨平台、高性能通用开发平台,其核心演进围绕运行时统一、类库裁剪与资源控制三大技术主线。自 .NET Core 1.0 实现零 Windows 依赖起,通过模块化 coreclr、多平台 JIT 及 SDK 自包含分发,奠定云原生基础;.NET 5 推动 BCL 源码统一与目标框架(TFM)标准化,实现‘一次编译、多端运行’;.NET 6 起的 Minimal Hosting 与 .NET 8 的 Native AOT 进一步将优化粒度下沉至方法级与编译期,达成内存精简、启动加速与容器深

dejz8829的专栏 431

1、网站可靠性工程(SRE):原理、实践与转型指南

本文深入探讨了网站可靠性工程(SRE)的核心原理、实践方法以及组织转型策略。从SRE的基本概念如服务水平指标(SLI)、服务水平目标(SLO)和错误预算入手,详细解析了如何通过SRE实现产品开发、运营和管理团队的高效协作。此外,还涵盖了SRE的实施步骤,包括现状评估、组织认同、基础设施建设、事件响应、错误预算政策制定以及组织结构设计等内容。最后,文章展望了SRE的未来发展,强调了服务目录、合规监管及SRE文化建设的重要性,为企业的现代化运营体系转型提供了全面指南。

xk7n92h3p5m的博客 147

【雷达】基于matlab合成孔径雷达干涉测量(InSAR)时序分析【含Matlab源码 9037期】

合成孔径雷达干涉测量(InSAR)时序分析 完整代码,包运行;可提供运行操作视频!适合小白!

订阅付费专栏Matlab(奶茶价版),可赠送奶茶价版付费专栏指定代码1份; 159
上一篇: ASP.NET File Upload Example
下一篇: XML 在 ASP 环境下的应用(推荐)
techweb
博客等级 码龄19年 226粉丝 3842原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值