Adding dll of modified classes ExternalFeed.cs ,StockList.cs to reflect the changes

[DarioCrivelli]

This is quite strange, so it's worth checking all the preconditions.
Please ensure that, before launching the Server, you followed the steps described in chapter 1.5 in

DOCS-SDKs\sdk_adapter_dotnet\doc\DotNet Adapters.pdf

which I resume below:

1. The files in

   DOCS-SDKs\sdk_adapter_dotnet\examples\DotNetStockListDe mo\Deployment\Deployment_DotNet_Server(custom)\dot net_1.1

   make up the Remote Server and the mounted Remote Adapters. The Remote Server should be launched manually, through the

   DOCS-SDKs\sdk_adapter_dotnet\examples\DotNetStockListDe mo\Deployment\Deployment_DotNet_Server(custom)\Dot NetCustomServer.bat

   script.
2. In order to communicate with the Remote Server, Lightstreamer Server should mount the so-called Proxy Adapter. This is accomplished by copying the contents of the

   DOCS-SDKs\sdk_adapter_dotnet\examples\DotNetStockListDe mo\Deployment\Deployment_LS

   directory in the Server's "adapters" subdirectory.
3. The client should be modified in order to ask for data from the Proxy Adapter rather than from the preinstalled StockListDemo adapter. To make this step simpler, the Proxy Adapter is preconfigured with the same name as the preinstalled StockListDemo adapter, so that no changes on the client are needed. However, the preinstalled StockListDemo adapter must be removed, to avoid conflicts; hence the

   adapters\StockList

   directory should be removed.

Dario

[indrajit]

Thanks Dario,

I removed LS from my machine and reconfigured it again and I followed each and every step explained by you but it of no use I am still getting the default stocklist demo data when I run and if I remove the same files which I posted in my previous post still it is behaving in the same way.

Dario if you have any working sample that is built on .net (may be a small one--like pushing a string Hello world or pushing numbers randomely) with steps to be followed to implement it on LightStreamer.

Thanks,

[DarioCrivelli]

Unfortunately, we haven't simpler examples available.

I would like to simplify the case and ensure that there are no misunderstandings. Please, try again with an incremental approach.

1. Start from a working installation of Lightstreamer. You should see the standard StockListDemo working. Your current configuration seems to be at this stage.
2. Remove all contents from the "adapters" directory and relaunch Lightstreamer Server. The StockListDemo should not display any data.
3. Copy the

   DOCS-SDKs\sdk_adapter_dotnet\examples\DotNetStockListDe mo\Deployment\Deployment_LS\StockList_sockets

   directory and all its contents into the "adapters" directory and relaunch Lightstreamer Server. The Server should block in the startup phase, trying to connect to the Remote Server and, of course, the StockListDemo should not be able to connect to Lightstreamer Server.

Only once the above steps are respected, we can move to the constructive phase.

[indrajit]

Yes Dario,

you are correct I tried those things previously, after launching the Deployment_DotNet_Server only we can launch the LS server. But my question here is where should I implement my custom DotnetStockListDemo.dll to reflect the changes.

[DarioCrivelli]

Ok, the next thing to clarify is that your dll is being used.
If you remove it from

DOCS-SDKs\sdk_adapter_dotnet\examples\DotNetStockListDe mo\Deployment\Deployment_DotNet_Server(custom)\dot net_1.1

does the Remote Server still start successfully?
If yes, because some caching by the .NET environment is in action under the hood, then you should at least change the names of your modified classes.

[michaelvb]

Hi,

I had the same problem. I didn't find it anything to do with .net in the end, but it is related to whether its using _your_ dll or not.

When you compile DotNetStockListDemoLauncher.exe, it contains a reference to the DotNetStockListDemo.dll . You need to make sure when you add this reference you browse to the folder containing your compiled .dll. Do not use the one contained in the DOCS-SDK etc lib folder. This is also why I think deleting the file from the sample deployment directory does not work as once again, its not looking at that dll.

Hope that helps


Michael