Development with Visual Studio Code - Revision history

Shr0x at 19:57, 14 December 2024

2024-12-14T19:57:12Z

← Older revision		Revision as of 19:57, 14 December 2024
Line 67:		Line 67:
	"request": "launch",		"request": "launch",
	"preLaunchTask": "compile",		"preLaunchTask": "compile",
	"program": "server.exe", // The RAGEMP server executable		"program": "ragemp-server.exe", // The RAGEMP server executable
	"args": [],		"args": [],
	"cwd": "${workspaceFolder}/../../../", // Or absolute path to your X:/RAGEMP/server-files/		"cwd": "${workspaceFolder}/../../../", // Or absolute path to your X:/RAGEMP/server-files/

Xabi: /* See also */

2024-10-10T08:33:04Z

Xabi: /* See also */

2024-10-10T08:32:12Z

Xabi: /* See also */

2024-10-10T08:31:47Z

Xabi at 19:50, 22 November 2022

2022-11-22T19:50:05Z

← Older revision		Revision as of 19:50, 22 November 2022
Line 1:		Line 1:
	This tutorial explains a basic to develop & debug a RAGE-MP resource / server-side script using [[wikipedia:Visual_Studio_Code\|VSCode]] on C# ~~bridge~~		This tutorial explains a basic to develop & debug a RAGE-MP resource / server-side script using [[wikipedia:Visual_Studio_Code\|VSCode]] on C#


Line 9:		Line 9:
	== Requirement ==		== Requirement ==
	* Visual Studio Code - [https://code.visualstudio.com/download Download]		* Visual Studio Code - [https://code.visualstudio.com/download Download]
	* .NET Core ~~SDK~~		* .NET Core 3.1- [https://dotnet.microsoft.com/download/dotnet-core/3.1 Download]
	** For RAGE 0.3.7, use version 2.2 - [https://dotnet.microsoft.com/download/dotnet-core/2.2 Download] (As of RAGE:MP 0.3.7, Server side uses version 2.0.3 and Client side uses version 2.2 so it's safe to install the latest which are backward compatible)
	** For RAGE 1.1 and above, use version 3.1 - [https://dotnet.microsoft.com/download/dotnet-core/3.1 Download] ~~(As of RAGE:MP 1.1, Server side uses version 3.1 and Client side uses version 2.2 so it's safe to install the latest which are backward compatible)~~
	* C# Extension for Visual Studio Code powered by OmniSharp - [https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp Download (in Visual Studio Code)]		* C# Extension for Visual Studio Code powered by OmniSharp - [https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp Download (in Visual Studio Code)]

	== Setting Up Project ==		== Setting Up Project ==
	# Open Visual Studio Code on '''~~bridge~~/resources''' ~~or '''dotnet/resources''~~' folder, ~~the path will be different for 0.3.7 and 1.1 versions~~		# Open Visual Studio Code on '''dotnet/resources''' folder (if you can't find this folder, just create it)
	# Create a new folder, example '''mygamemode''' then select the folder		# Create a new folder, example '''mygamemode''' then select the folder
	# Open the terminal <kbd>'''Ctrl'''</kbd>+<kbd>'''`'''</kbd> (control + tilde)		# Open the terminal <kbd>'''Ctrl'''</kbd>+<kbd>'''`'''</kbd> (control + tilde)
	# Enter ~~<tt>></tt><code>dotnet new classlib -f netcoreapp2</code> if using 0.3.7 or~~ <tt>></tt><code>dotnet new classlib -f netcoreapp3.1</code> ~~if using 1.1~~ to create a new .NET Core class library		# Enter <tt>></tt><code>dotnet new classlib -f netcoreapp3.1</code> to create a new .NET Core class library
	~~<tt><</tt>script>~~
	# A <tt>.csproj</tt> file will be created, click to edit it		# A <tt>.csproj</tt> file will be created, click to edit it
	## [https://docs.microsoft.com/en-us/dotnet/standard/frameworks#how-to-specify-target-frameworks Change the TargetFramework] to ~~<code>netcoreapp2.0</code> or~~ <code>netcoreapp3.1</code>		## [https://docs.microsoft.com/en-us/dotnet/standard/frameworks#how-to-specify-target-frameworks Change the TargetFramework] to <code>netcoreapp3.1</code>
	## [https://docs.microsoft.com/en-us/dotnet/core/versions/selection#self-contained-deployments-include-the-selected-runtime Set the RuntimeFrameworkVersion] tothe one matching your serverside .NET Core SDK version		## [https://docs.microsoft.com/en-us/dotnet/core/versions/selection#self-contained-deployments-include-the-selected-runtime Set the RuntimeFrameworkVersion] tothe one matching your serverside .NET Core SDK version
	## Include <tt>GTANetworkAPI</tt> by adding reference to ~~'''bridge/runtime/Bootstrapper.dll''' or~~ '''dotnet/runtime/Bootstrapper.dll'''		## Include <tt>GTANetworkAPI</tt> by adding reference to '''dotnet/runtime/Bootstrapper.dll'''
	## Your <tt>mygamemode.csproj</tt> should look like this:		## Your <tt>mygamemode.csproj</tt> should look like this:
	<pre>		<pre>
	<Project Sdk="Microsoft.NET.Sdk">		<Project Sdk="Microsoft.NET.Sdk">

	~~<!-- If building a 0.3.7 server use this configuration -->~~
	~~<PropertyGroup>~~
	~~<TargetFramework>netcoreapp2.0</TargetFramework>~~
	~~<RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion>~~
	~~</PropertyGroup>~~

	~~<!-- If building a 1.1 server use this configuration -->~~
	<PropertyGroup>		<PropertyGroup>
	<TargetFramework>netcoreapp3.1</TargetFramework>		<TargetFramework>netcoreapp3.1</TargetFramework>
Line 157:		Line 147:
	<gallery widths=500px heights=94px>Image:Meta-example.JPG</gallery>		<gallery widths=500px heights=94px>Image:Meta-example.JPG</gallery>

	Note that after running compile task, your <tt>.cs</tt> scripts will be compiled into <tt>.dll</tt> by default located on <code>bin/Debug/~~netcoreapp2~~.0/</code> folder relative to your resource directory.		Note that after running compile task, your <tt>.cs</tt> scripts will be compiled into <tt>.dll</tt> by default located on <code>bin/Debug/netcoreapp3.1/</code> folder relative to your resource directory.

	If you are not sure why your <tt>.dll</tt> does not work, try running the server with raw <tt>Class1.cs</tt> source code (uncomment the Uncompiled and comment the Compiled script tag).		If you are not sure why your <tt>.dll</tt> does not work, try running the server with raw <tt>Class1.cs</tt> source code (uncomment the Uncompiled and comment the Compiled script tag).

	=== Configuring settings.xml file ===		=== Configuring settings.xml file ===
	# Edit ~~'''bridge/[https://wiki.gtanet.work/index.php?title=settings.xml settings.xml]''' or~~ '''dotnet/[https://wiki.gtanet.work/index.php?title=settings.xml settings.xml]''' file in your server folder, add your resource like the following:		# Edit '''dotnet/[https://wiki.gtanet.work/index.php?title=settings.xml settings.xml]''' file in your server folder, add your resource like the following:
	<pre>		<pre>
	<?xml version="1.0"?>		<?xml version="1.0"?>
Line 211:		Line 201:
	Simply, click on menu '''Terminal'''>'''Run Task...''' then select '''release'''		Simply, click on menu '''Terminal'''>'''Run Task...''' then select '''release'''

	You can find your <tt>.dll</tt> in <code>bin/Release/~~netcoreapp2~~.0/</code> as you may notice it contains cleaner files, since we configured to not copy the <tt>.dll</tt> files from runtime folder with the <code><Private></code> option.		You can find your <tt>.dll</tt> in <code>bin/Release/netcoreapp3.1/</code> as you may notice it contains cleaner files, since we configured to not copy the <tt>.dll</tt> files from runtime folder with the <code><Private></code> option.
	This build will be not debugable as the symbols are already removed and optimized for run time.		This build will be not debugable as the symbols are already removed and optimized for run time.

Line 237:		Line 227:
	\|-		\|-
	!		!
	! Server-side ~~Bridge~~ (Compiled)		! Server-side (Compiled)
	! Server-side (Raw)		! Server-side (Raw)
	! Client-side		! Client-side
Line 246:		Line 236:
	\|-		\|-
	! Dependency		! Dependency
	\| colspan="2" \| <tt>Bootstrapper.dll</tt> runtimes ~~& <tt>bridge.dll</tt> plugin~~		\| colspan="2" \| <tt>Bootstrapper.dll</tt> runtimes
	\| <tt>rage-sharp.dll</tt> runtimes		\| <tt>rage-sharp.dll</tt> runtimes
	\|-		\|-
	! Compile Time		! Compile Time
	\| By server developer with C# Compiler (in SDK)		\| By server developer with C# Compiler (in SDK)
	\| By <tt>server.exe</tt>		\| By <tt>ragemp-server.exe</tt>
	\| By <tt>ragemp_v.exe</tt>		\| By <tt>ragemp_v.exe</tt>
	\|-		\|-
	! .NET Core Version		! .NET Core Version
	\| colspan="2" \| 2.~~0.3~~ <sup>1)</sup>		\| colspan="2" \| 3.1 <sup>1)</sup>
	\| 2.2.0 <sup>2)</sup>		\| 2.2.0 <sup>2)</sup>
	\|-		\|-
Line 262:		Line 252:
	\| colspan="2" \| RAGE MP app built in error handling & logging		\| colspan="2" \| RAGE MP app built in error handling & logging
	\|}		\|}
	~~Notes:~~
	* <sup>1)</sup> As of 0.3.7 based on <tt>.version</tt> file found in '''RAGEMP/server-files/bridge/runtime/''' folder
	* <sup>2)</sup> As of 0.3.7 based on <tt>.version</tt> file found in '''RAGEMP/dotnet/''' folder

	== See also ==		== See also ==

Xabi: /* Configuring bridge setting */

2022-08-18T16:58:02Z

Configuring bridge setting

← Older revision		Revision as of 16:58, 18 August 2022
Line 161:		Line 161:
	If you are not sure why your <tt>.dll</tt> does not work, try running the server with raw <tt>Class1.cs</tt> source code (uncomment the Uncompiled and comment the Compiled script tag).		If you are not sure why your <tt>.dll</tt> does not work, try running the server with raw <tt>Class1.cs</tt> source code (uncomment the Uncompiled and comment the Compiled script tag).

	=== Configuring ~~bridge setting~~ ===		=== Configuring settings.xml file ===
	# Edit '''bridge/[https://wiki.gtanet.work/index.php?title=settings.xml settings.xml]''' file in your server folder, add your resource like the following:		# Edit '''bridge/[https://wiki.gtanet.work/index.php?title=settings.xml settings.xml]''' or '''dotnet/[https://wiki.gtanet.work/index.php?title=settings.xml settings.xml]''' file in your server folder, add your resource like the following:
	<pre>		<pre>
	<?xml version="1.0"?>		<?xml version="1.0"?>

Xabi: Modified requirements to match both 0.3.7 and 1.1+ versions

2020-08-25T08:59:51Z

Modified requirements to match both 0.3.7 and 1.1+ versions

← Older revision		Revision as of 08:59, 25 August 2020
Line 9:		Line 9:
	== Requirement ==		== Requirement ==
	* Visual Studio Code - [https://code.visualstudio.com/download Download]		* Visual Studio Code - [https://code.visualstudio.com/download Download]
	* .NET Core SDK version 2.2 - [https://dotnet.microsoft.com/download/dotnet-core/2.2 Download] (As of RAGE:MP 0.3.7, Server side uses version 2.0.3 and Client side uses version 2.2.0 so it's safe to install the latest which are backward compatible)		* .NET Core SDK
			** For RAGE 0.3.7, use version 2.2 - [https://dotnet.microsoft.com/download/dotnet-core/2.2 Download] (As of RAGE:MP 0.3.7, Server side uses version 2.0.3 and Client side uses version 2.2 so it's safe to install the latest which are backward compatible)
			** For RAGE 1.1 and above, use version 3.1 - [https://dotnet.microsoft.com/download/dotnet-core/3.1 Download] (As of RAGE:MP 1.1, Server side uses version 3.1 and Client side uses version 2.2 so it's safe to install the latest which are backward compatible)
	* C# Extension for Visual Studio Code powered by OmniSharp - [https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp Download (in Visual Studio Code)]		* C# Extension for Visual Studio Code powered by OmniSharp - [https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp Download (in Visual Studio Code)]

	== Setting Up Project ==		== Setting Up Project ==
	# Open Visual Studio Code on '''bridge/resources''' folder		# Open Visual Studio Code on '''bridge/resources''' or '''dotnet/resources''' folder, the path will be different for 0.3.7 and 1.1 versions
	# Create a new folder, example '''mygamemode''' then select the folder		# Create a new folder, example '''mygamemode''' then select the folder
	# Open the terminal <kbd>'''Ctrl'''</kbd>+<kbd>'''`'''</kbd> (control + tilde)		# Open the terminal <kbd>'''Ctrl'''</kbd>+<kbd>'''`'''</kbd> (control + tilde)
	# Enter <tt>></tt><code>dotnet new classlib -f netcoreapp2</code> to create a new .NET Core class library		# Enter <tt>></tt><code>dotnet new classlib -f netcoreapp2</code> if using 0.3.7 or <tt>></tt><code>dotnet new classlib -f netcoreapp3.1</code> if using 1.1 to create a new .NET Core class library
			<tt><</tt>script>
	# A <tt>.csproj</tt> file will be created, click to edit it		# A <tt>.csproj</tt> file will be created, click to edit it
	## [https://docs.microsoft.com/en-us/dotnet/standard/frameworks#how-to-specify-target-frameworks Change the TargetFramework] to <code>netcoreapp2.0</code>		## [https://docs.microsoft.com/en-us/dotnet/standard/frameworks#how-to-specify-target-frameworks Change the TargetFramework] to <code>netcoreapp2.0</code> or <code>netcoreapp3.1</code>
	## [https://docs.microsoft.com/en-us/dotnet/core/versions/selection#self-contained-deployments-include-the-selected-runtime Set the RuntimeFrameworkVersion] ~~to 2~~.~~0.3~~		## [https://docs.microsoft.com/en-us/dotnet/core/versions/selection#self-contained-deployments-include-the-selected-runtime Set the RuntimeFrameworkVersion] tothe one matching your serverside .NET Core SDK version
	## Include <tt>GTANetworkAPI</tt> by adding reference to '''dotnet/runtime/Bootstrapper.dll'''		## Include <tt>GTANetworkAPI</tt> by adding reference to '''bridge/runtime/Bootstrapper.dll''' or '''dotnet/runtime/Bootstrapper.dll'''
	## Your <tt>mygamemode.csproj</tt> should look like this:		## Your <tt>mygamemode.csproj</tt> should look like this:
	<pre>		<pre>
	<Project Sdk="Microsoft.NET.Sdk">		<Project Sdk="Microsoft.NET.Sdk">

			<!-- If building a 0.3.7 server use this configuration -->
	<PropertyGroup>		<PropertyGroup>
	<TargetFramework>netcoreapp2.0</TargetFramework>		<TargetFramework>netcoreapp2.0</TargetFramework>
	<RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion>		<RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion>
			</PropertyGroup>

			<!-- If building a 1.1 server use this configuration -->
			<PropertyGroup>
			<TargetFramework>netcoreapp3.1</TargetFramework>
	</PropertyGroup>		</PropertyGroup>

Line 35:		Line 44:

	<ItemGroup>		<ItemGroup>
	<Reference Include="~~GTANetworkAPI~~">		<Reference Include="Bootstrapper">
	<HintPath>..\..\runtime\Bootstrapper.dll</HintPath~~> <!-- Or absolute path to your X:/RAGEMP/server-files/dotnet/runtime/Bootstrapper.dll --~~>		<HintPath>..\..\runtime\Bootstrapper.dll</HintPath>
	<Private Condition="'$(Configuration)\|$(Platform)'=='Release\|AnyCPU'">False</Private>		<Private Condition="'$(Configuration)\|$(Platform)'=='Release\|AnyCPU'">False</Private>
	</Reference>		</Reference>
Line 146:		Line 155:
	# Create a new file [https://wiki.gtanet.work/index.php?title=meta.xml meta.xml] in your resource folder (if not exist)		# Create a new file [https://wiki.gtanet.work/index.php?title=meta.xml meta.xml] in your resource folder (if not exist)
	# Put some resource information, and add the <tt>mygamemode.dll</tt> file		# Put some resource information, and add the <tt>mygamemode.dll</tt> file
	<~~pre>~~		<gallery widths=500px heights=94px>Image:Meta-example.JPG</gallery>
	~~<meta>~~
	~~<info name~~=~~"My Gamemode" description~~=~~"My C# bridge gamemode Resource" />~~
	~~<!-- Uncompiled: -->~~
	~~<!-- <script src="Class1.cs" /> --~~>
	~~<!-- Compiled~~: -->
	~~<script src="bin/Debug/netcoreapp2.0/mygamemode~~.~~dll" />~~
	</~~meta~~>
	~~</pre>~~
	Note that after running compile task, your <tt>.cs</tt> scripts will be compiled into <tt>.dll</tt> by default located on <code>bin/Debug/netcoreapp2.0/</code> folder relative to your resource directory.		Note that after running compile task, your <tt>.cs</tt> scripts will be compiled into <tt>.dll</tt> by default located on <code>bin/Debug/netcoreapp2.0/</code> folder relative to your resource directory.

Line 213:		Line 215:

	Proceed to upload these <tt>.dll</tt> file to your server, and be sure to set your '''meta.xml''' differently as it will be using the non-debugged version.		Proceed to upload these <tt>.dll</tt> file to your server, and be sure to set your '''meta.xml''' differently as it will be using the non-debugged version.
	<~~pre>~~		<gallery widths=500px heights=54px>Image:Meta-final.JPG</gallery>
	~~<meta>~~
	~~<info name~~=~~"My Gamemode" description~~=~~"My C# bridge gamemode Resource" /~~>
	~~<script src="bin/Release/netcoreapp2.0/mygamemode~~.~~dll" />~~
	~~</meta>~~
	</~~pre~~>

	You might want to have the <tt>.pdb</tt> file together with it, it will create useful traceable dump in case your code causes server crash during runtime, even though it is not really possible to debug it.		You might want to have the <tt>.pdb</tt> file together with it, it will create useful traceable dump in case your code causes server crash during runtime, even though it is not really possible to debug it.

Vula: /* Setting Up Project */

2020-08-16T06:39:47Z

Setting Up Project

← Older revision		Revision as of 06:39, 16 August 2020
Line 20:		Line 20:
	## [https://docs.microsoft.com/en-us/dotnet/standard/frameworks#how-to-specify-target-frameworks Change the TargetFramework] to <code>netcoreapp2.0</code>		## [https://docs.microsoft.com/en-us/dotnet/standard/frameworks#how-to-specify-target-frameworks Change the TargetFramework] to <code>netcoreapp2.0</code>
	## [https://docs.microsoft.com/en-us/dotnet/core/versions/selection#self-contained-deployments-include-the-selected-runtime Set the RuntimeFrameworkVersion] to 2.0.3		## [https://docs.microsoft.com/en-us/dotnet/core/versions/selection#self-contained-deployments-include-the-selected-runtime Set the RuntimeFrameworkVersion] to 2.0.3
	## Include <tt>GTANetworkAPI</tt> by adding reference to '''~~bridge~~/runtime/Bootstrapper.dll'''		## Include <tt>GTANetworkAPI</tt> by adding reference to '''dotnet/runtime/Bootstrapper.dll'''
	## Your <tt>mygamemode.csproj</tt> should look like this:		## Your <tt>mygamemode.csproj</tt> should look like this:
	<pre>		<pre>
Line 36:		Line 36:
	<ItemGroup>		<ItemGroup>
	<Reference Include="GTANetworkAPI">		<Reference Include="GTANetworkAPI">
	<HintPath>..\..\runtime\Bootstrapper.dll</HintPath> <!-- Or absolute path to your X:/RAGEMP/server-files/~~bridge~~/runtime/Bootstrapper.dll -->		<HintPath>..\..\runtime\Bootstrapper.dll</HintPath> <!-- Or absolute path to your X:/RAGEMP/server-files/dotnet/runtime/Bootstrapper.dll -->
	<Private Condition="'$(Configuration)\|$(Platform)'=='Release\|AnyCPU'">False</Private>		<Private Condition="'$(Configuration)\|$(Platform)'=='Release\|AnyCPU'">False</Private>
	</Reference>		</Reference>

RoboN1X at 15:10, 23 May 2019

2019-05-23T15:10:26Z

← Older revision		Revision as of 15:10, 23 May 2019
Line 5:		Line 5:
	[[#Client-side\|See the comparison below]].		[[#Client-side\|See the comparison below]].

	This tutorial will mainly describe about compiling your server-side resource into <tt>.dll</tt> binary which you can attach a debugger on it. A similar step can be also done in [[wikipedia:Visual Studio]], except the launch & task part.		This tutorial will mainly describe about compiling your server-side resource into <tt>.dll</tt> binary which you can attach a debugger on it. A similar step can be also done in [[wikipedia:Visual Studio\|Visual Studio IDE]], except the launch & task part.

	== Requirement ==		== Requirement ==
Line 36:		Line 36:
	<ItemGroup>		<ItemGroup>
	<Reference Include="GTANetworkAPI">		<Reference Include="GTANetworkAPI">
	<HintPath>..\..\runtime\Bootstrapper.dll</HintPath> <!-- Or absolute path to your /RAGEMP/server-files/bridge/runtime/Bootstrapper.dll -->		<HintPath>..\..\runtime\Bootstrapper.dll</HintPath> <!-- Or absolute path to your X:/RAGEMP/server-files/bridge/runtime/Bootstrapper.dll -->
	<Private Condition="'$(Configuration)\|$(Platform)'=='Release\|AnyCPU'">False</Private>		<Private Condition="'$(Configuration)\|$(Platform)'=='Release\|AnyCPU'">False</Private>
	</Reference>		</Reference>
Line 70:		Line 70:
	"program": "server.exe", // The RAGEMP server executable		"program": "server.exe", // The RAGEMP server executable
	"args": [],		"args": [],
	"cwd": "${workspaceFolder}/../../../", // Or absolute path to your /RAGEMP/server-files/		"cwd": "${workspaceFolder}/../../../", // Or absolute path to your X:/RAGEMP/server-files/
	"stopAtEntry": false,		"stopAtEntry": false,
	"console": "externalTerminal",		"console": "externalTerminal",
Line 229:		Line 229:
	<ItemGroup>		<ItemGroup>
	<Reference Include="RAGE">		<Reference Include="RAGE">
	<HintPath>..\..\..\dotnet\rage-sharp.dll</HintPath> <!-- Or absolute path to your /RAGEMP/dotnet/rage-sharp.dll -->		<HintPath>..\..\..\dotnet\rage-sharp.dll</HintPath> <!-- Or absolute path to your X:/RAGEMP/dotnet/rage-sharp.dll -->
	<Private>False</Private>		<Private>False</Private>
	</Reference>		</Reference>

RoboN1X at 15:07, 23 May 2019

2019-05-23T15:07:49Z

← Older revision		Revision as of 15:07, 23 May 2019
Line 2:		Line 2:


	Note ~~that~~ it is not required for you to compile the .cs scripts to run the resource, you can let the server compile ~~itself~~ when server starts.		Note: it is not required for you to compile the .cs scripts to run the resource, you can let the server compile them when server starts.
	[[#Client-side\|See the comparison below]].		[[#Client-side\|See the comparison below]].

	This tutorial will mainly describe about compiling your server-side resource into <tt>.dll</tt> binary which you can attach a debugger on it.		This tutorial will mainly describe about compiling your server-side resource into <tt>.dll</tt> binary which you can attach a debugger on it. A similar step can be also done in [[wikipedia:Visual Studio]], except the launch & task part.

	== Requirement ==		== Requirement ==
	* Visual Studio Code [https://code.visualstudio.com/download Download]		* Visual Studio Code - [https://code.visualstudio.com/download Download]
	* .NET Core SDK 2.2 [https://dotnet.microsoft.com/download/dotnet-core/2.2 Download] (As of RAGE:MP 0.3.7, Server side uses version 2.0.3 and Client side uses version 2.2.0 so it's safe to install the latest which are backward compatible)		* .NET Core SDK version 2.2 - [https://dotnet.microsoft.com/download/dotnet-core/2.2 Download] (As of RAGE:MP 0.3.7, Server side uses version 2.0.3 and Client side uses version 2.2.0 so it's safe to install the latest which are backward compatible)
	* C# Extension for Visual Studio Code powered by OmniSharp [https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp Download]		* C# Extension for Visual Studio Code powered by OmniSharp - [https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp Download (in Visual Studio Code)]

	== Setting Up Project ==		== Setting Up Project ==
Line 223:		Line 223:

	== Client-side ==		== Client-side ==
	You can also do similar thing to work with client-side scripts. However, please note that in RAGE MP Client-side C-Sharp scripts are NOT compiled nor build into <tt>.dll</tt>. Which means you cannot debug it like in this tutorial.		You can also do similar thing to work with client-side scripts, except you do not deal with launch or task commands. However, please note that in RAGE MP Client-side C-Sharp scripts are NOT compiled nor build into <tt>.dll</tt>. Which means you cannot debug it like in this tutorial.

	You can still make the project, reference to '''rage-sharp.dll''' in '''RAGEMP/dotnet/''' folder to get IntelliSense auto completion benefit in VSCode, similar way we did on Bootstrapper:		You can still make the project, reference to '''rage-sharp.dll''' in '''RAGEMP/dotnet/''' folder to get IntelliSense auto completion benefit in VSCode, similar way we did on Bootstrapper:
Line 234:		Line 234:
	</ItemGroup>		</ItemGroup>
	</pre>		</pre>
	And you just have to save the <tt>.cs</tt> file, they will be downloaded to your player's RAGE-MP client as how you configured it.		And you just have to save the <tt>.cs</tt> file, they will be downloaded to your player's RAGE-MP client and will be compiled as how you configured it.

	{\| class="wikitable		{\| class="wikitable

← Older revision		Revision as of 08:33, 10 October 2024
Line 255:		Line 255:
	== See also ==		== See also ==
	* [[Getting Started with Development]]		* [[Getting Started with Development]]
	* [[Server-side events]]		* [[Server-side events]] (or in [[Server-side_CSharp_events\|C#]])
	* [[Server-side functions]]		* [[Server-side functions]] (or in [[Server-side_CSharp_function\|C#]])
	* [[Client-side events]] (or in [[Client-side_CSharp_events\|C#]])		* [[Client-side events]] (or in [[Client-side_CSharp_events\|C#]])
	* [[Client-side functions]] (or in [[Client-side_CSharp_functions\|C#]])		* [[Client-side functions]] (or in [[Client-side_CSharp_functions\|C#]])

	[[Category:Tutorials]]		[[Category:Tutorials]]

← Older revision		Revision as of 08:32, 10 October 2024
Line 255:		Line 255:
	== See also ==		== See also ==
	* [[Getting Started with Development]]		* [[Getting Started with Development]]
	* [https://wiki.gtanet.work/index.php?title=Getting_Started_with_Development Getting started with Development on C# Bridge Server]
	* [[Server-side events]]		* [[Server-side events]]
	* [[Server-side functions]]		* [[Server-side functions]]

← Older revision		Revision as of 08:31, 10 October 2024
Line 256:		Line 256:
	* [[Getting Started with Development]]		* [[Getting Started with Development]]
	* [https://wiki.gtanet.work/index.php?title=Getting_Started_with_Development Getting started with Development on C# Bridge Server]		* [https://wiki.gtanet.work/index.php?title=Getting_Started_with_Development Getting started with Development on C# Bridge Server]
	* [[Server-side events]] ~~(or in [https://wiki.gtanet.work/index.php?title=Scripting_Events C#] bridge)~~		* [[Server-side events]]
	* [[Server-side functions]] ~~(or in [https://wiki.gtanet.work/index.php?title=Server_Scripting_Functions C#] bridge)~~		* [[Server-side functions]]
	* [[Client-side events]] (or in [[Client-side_CSharp_events\|C#]])		* [[Client-side events]] (or in [[Client-side_CSharp_events\|C#]])
	* [[Client-side functions]] (or in [[Client-side_CSharp_functions\|C#]])		* [[Client-side functions]] (or in [[Client-side_CSharp_functions\|C#]])

	[[Category:Tutorials]]		[[Category:Tutorials]]